If you’re using dSupportSuite and self-hosting your own FTP server, this does NOT apply to you!
If you’re using an old dSupportSuite purchase with our hosted dCloud services (for which you are paying monthly or purchased lifetime access) then this does apply to you.
We’re in the process of migrating the aging dCloud server to a new server, in order to take advantage of the latest security updates. Currently we’re waiting for DNS changes (pointing to the new server) to fully propagate; we expect the process to be complete within the next day or two. After that time we will bring down the old server for good.
We have observed that some client IDs created this weekend have had issues when downloading their configs from the client software, which has failed or downloaded incorrect/older configurations from the server. This has occurred where DNS hasn’t propagated or DNS is still caching old server settings on the client PC (which was contacting the old server) whereas the PC with Mgmt Console was updating configs on the new server; the issue can also occur in reverse.
As of right now, both servers are up and running with a data sync between them (the server with the newest files will propagate them to the other server.) We hope that the current data sync between servers will alleviate any such issues until DNS has propagated fully and caches are flushed.
In the meantime, if you are still experiencing issues, then on your Mgmt Console PC you may want to start an administrative command prompt and run “ipconfig /flushdns” from there to clear the DNS cache on your local PC. If you’re installing dSupportSuite on a client system it is a good idea to do it from there as well. If you ping “cloud.foolishit.com” or “cloud.d7xtech.com” the return IP address should end in .171 to indicate you are connecting to the new server (the old one ends in .154) — but again we do believe the server data sync will alleviate any issues going forward.
Once we’re confident that DNS has propagated fully we will bring down the old server and it’s absence should hopefully force all PCs attempting to connect to clear this entry from DNS cache and request a new address from their DNS servers.
We appreciate your patience if you have experienced any such issues related to the server migration; they will soon be resolved.