Digital Ocean Issues after altering Droplet name?

[ReessKennedy]

Cloudron Issues

Having Cloudron issues suddenly after over year of stable usage on a droplet on Digital Ocean where Cloudron was initially installed via Digital Ocean's app installer tool. Spent many hours yesterday trying to solve on my own and reading forum notes on similar issues and still failed ... Details of my this effort below.

What is happening

2 apps and the dashboard my.mydomain.com went unreachable a couple days ago with this message I see is pretty common during config issues based on forum searching:

"You are seeing this page because the DNS record of my.domain.info is set to this server's IP but Cloudron has no app configured for this domain."

Oddly, one of the apps I have installed in Vault Warden and though I do see this message when I hit the web ui for Vault Warden it appears I am still able to connect to the app inside the Chrome Extension.

Details

• I used nslookup for the my.mydomain.com domain and it is pointing to the correct IP for the Cloudron install, which makes sense since I am getting this message
• The subdomains for the two apps I have installed both also receive this message and when I ping these domains they also resolve to the IP of the droplet.

Conclusions from this: All domains seem to have proper DNS settings so it seems to be a Cloudron config issues.

Possible things that caused

Changed name of droplet.

but this is a superficial change that I think only occurs in a Digital Ocean database just for labeling and does not impact any server config.

Started trying using designated IP

• I turned on Digital Ocean's dedicated IP feature which allows me to choose a dedicated IP and then point it to a droplet.
• That said, even though I turned this on I disabled it for this droplet and continued pointing my domains to the droplet's IP address.
• There was a time I may have tried pointing the root my.mydomain.com domain to the new, dedicated IP instead of original but then I switched it back and given the message I continue to get it does not, again, seem to be a resolution issue and instead looks like it is a config issue.

Things I checked

Think I tried everything on troubleshooting page here: Tried here: https://docs.cloudron.io/troubleshooting/

All systems seem like they are working fine

System	Status
Nginx	- Active
Unbound	- Active
Docker	- Active
MySQL	- Active

Other things

• Resized the droplet to give it more memory in hopes this might help
• Restarted droplet a few times
• Tried to change host name at one point but then changed it back ...
  • Used sudo hostnamectl set-hostname new-hostname
  • And then checked here sudo nano /etc/hosts
• Used this a bunch sudo systemctl list-units | grep cloudron
  cloudron-disable-thp.service. loaded active exited Disable Transparent Huge Pages (THP)
  cloudron-firewall.service loaded active exited Cloudron Firewall
  cloudron-resize-fs.service loaded active exited Cloudron FS Resizer
  cloudron-syslog.service loaded active running Cloudron Syslog

One last idea I had was wondering whether the domains associated with this install were changed somehow? .. I tried to see if I could use command line to view the config file for this which led me to to Cloudron CLI ...

Cloudron CLI

I started trying to install Cloudron CLI on my Mac but then ran into Node install issues and realized I had spent all day on this and then started to cry a bit and question why I love computers and self-hosting so much and wondering whether I even do love them or is it something else?

[nebulon]

If the app domains correctly resolve to your Cloudron's IP then most likely something is off with the nginx configs on the system. In this case, maybe try to resubmit the app's location form (change the subdomain back and forth) and the nginx reverse proxy configs should be recreated.

[girish]

@ReessKennedy said in Digital Ocean Issues after altering Droplet name?:

Changed name of droplet.

but this is a superficial change that I think only occurs in a Digital Ocean database just for labeling and does not impact any server config.

In DigitalOcean, the name of the droplet is also the reverse/PTR address for the IP address. Just something to remember, this is not the reason your Cloudron is unreachable though.

All systems seem like they are working fine

Can you also run cloudron-support --troubleshoot on the server?