Skip to content

Best Practices for Working with a Xojo Cloud Server

Since I’ve been asked about this by new and current Xojo Cloud users, let’s cover some basic best practices for everyone.

  1. Don’t ping or port scan the server. Our adaptive firewall is designed to look for behavior which looks like the type of traffic that comes just before an attack. Pings and Port Scans will get you blocked from your own server for a period of time. If your server isn’t accessible, head on over to and type in your server’s IP address. That will help us understand if the problem is on your end or ours. Restarting or Deploying to your server will clear this up for you.
  2. Stats only work after you have deployed. Displaying stats in the IDE can be processor intensive for your Xojo Cloud server, especially if there is more than one user requesting them. To prevent this, statistics are only available to users who have been specifically whitelisted on the firewall and the easiest way to do that is to deploy, even if it’s a simple empty app.
  3. Databases require memory and processor cores. When adding a database to your Xojo Cloud server, it’s important to remember that they do require memory and CPU processor cores to run. For the best experience, we recommend that users upgrade to a Xojo Cloud server with at least 4 vCPUs.