@bossbarnes07 It seems an 'A' record with the subdomain 'my' is missing. It should point to your IP (209.97.x.x). Cloudron should have added this automatically, I wonder why it didn't get added. Can you add an A record manually and then go to your server and do "systemctl restart box". You can then visit https://ip again and re-do the setup.
@girish Will do. It's actually not the first time I've run into the problem and a re-fresh of the API credentials solved the problem, although this is the first time I specifically observed that it was a 500 error vs. a 401.
@imouthesmp You can just restart the droplet. No need to stop/shutdown apps. All the apps and Cloudron dashboard will start automatically after a reboot. You can also resize the droplet (CPU/Disk/RAM) as you see fit and Cloudron will adapt automatically.
Admin credentials for mongo are really internal/implementation details. In general, do not make configuration changes to the mongodb instance because it may not work across all apps. This is the reason why all the databases are "locked" down and not exposed to users for easy access.
That warning said, you can do docker inspect mongodb | grep CLOUDRON_MONGODB_ROOT_PASSWORD to get the root password.
Okay, that makes sense. Thank you for the quick reply. 🙂
I wonder if it would make sense to add a feature where we can set the IP address to accommodate floating IP's in providers like DigitalOcean, so that the DNS records automatically setup by Cloudron in DigitalOcean would be using the floating IP instead. Without such a feature, it kind of removes the ability to have a sort-of manual failover method which is one of the main purposes of a floating IP from DigitalOcean (along with a secondary use-case of setting up a new server to replace an old one and moving the floating IP to the new one when ready, eliminating the need to update a whole bunch of DNS records). It would be nice, I think, to have Cloudron use a floating IP that we give it even if it means we have to set it manually in Cloudron first since it can't detect it automatically. The main reason for this is that whenever I switch a server, for example, nothing really needs to be changed at all, leaving downtime to a minimum if it exists at all during a server switch.