@RichardAlbrecht @Greg OLone
I was unable to connect until I deployed an app from Xojo. It then connected fine. So how can there not be a problem to solve?
Your inability to connect to the server was because of how you had been attempting to communicate with the server previously. Deploying to your server temporarily lifts some of the security restrictions so that you can connect and upload an app from your computer, but acting like a potential intruder certainly can surely get you blocked.
For example, Pinging has an ever increasing penalty, so the more you use it, the longer you’ll be denied access. Also, attempting to connect on multiple ports in a short period of time also carries a penalty, so trying to connect to ssh and one of the databases directly and http might also have gotten you blocked for a time.
The point is that a Xojo Cloud server is not just a Virtual Private Server with a simple firewall and some software to interact with our IDEs. its more equivalent to a managed server with an adaptive firewall, an intrusion detection system, Security Enhanced Linux and regular system updates. Think of the difference between having a simple lock on a doorknob and also having a deadbolt, a German Shepard, an alarm system and a hundred kilo safe when trying to protect your valuables. Yes, you may never need all that stuff and they may be inconvenient, but if you do, you’re much better off having had it there in the first place. Unfortunately, the only way to tell the good guys from the bad is by how they behave. Just like the home security example, if you try to break in or act aggressively, you’re going to attract someones attention, the police are probably going to show up and you’ll almost definitely get bitten.
We’ve found that the most important thing is not to get frustrated if you’re running into problems. I know it sounds counterintuitive, but people who have any previous server experience tend to start aggressively trying to contact their server when something goes awry. To the server, that looks exactly like the preamble to an attack. The secret is to take a deep breath and give the server’s security systems a chance to settle down. Once they do, you’ll be granted access again. The trick being that if you try again too soon, you will just extend your timeout period. 5 or 10 minutes ought to do it... or as we’ve said before... just deploy a simple app from the IDE.