@girish Finally, I would like to say that I haven't quite figured out what the problem was. I had used Cloudron bare metal. In the last few days I switched to Windows Server and have Cloudron running in a Linux VM via Hyper V. I then assigned a manual IP there and the problem no longer occurs. I guess it would have been fixed before with a manual IP as well.

This is not possible, no. The structure of data of both the apps are quite different. Also, when you backup Cloudron apps, the code is not part of the backup. LAMP app is sort of a special case here since the code is part of the "data" and part of backup . You should be able to migrate it manually though. Import database and copy over the needed files.

@girish Thanks for answering, I will try it and if I still face any issue, I will update by starting my own thread.

@girish it works! Thanks a lot.

you can check it your self with GRC shields up https://www.grc.com/x/ne.dll?bh0bkyd2

Thank you @girish , this worked. For those coming through in the future note that cloudron-support may ask you to reboot and run again, keep an eye out for it.

Many thanks, after deleting config file for freshrss the restart of nginx went OK.

@humptydumpty thanks for the info! Cloudron should not be affected, no. We don't rely on name servers IPs. Also, I think this is for people having vanity nameservers, which Cloudron does not support.

Thank you @girish - I'll test with v8 and report back thereafter in case of need.

Thank you @girish - Sounds promising. Looking forward to v8.

@estudios507 If you want to open up an arbitrary port like 8000 from your server, then you have to build a custom app for this . See https://docs.cloudron.io/packaging/tutorial/ . The custom app has to expose 8000 using https://docs.cloudron.io/packaging/manifest/#tcpports . There is no other way on Cloudron for an app to expose a custom port.

@AmbroiseUnly yeah, good idea. I will add it to our internal list to check for backup existence to give quicker feedback.

@paliwalneeraj this is not the right forum for AKS help (or dockurr or Windows). This is the Cloudron forum. It's a different product.

I should have changed DO DNS to AWS before deleting it then, but I didn't quite understand how to do that either. I guess that'll be the worry of the next person who runs into a similar situation.

I will mark this as solved, but if you hit this again please let us know.

@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?

Yup, you are right that Cloudron needs IPv4 currently. IPv6 only setup is coming only in Cloudron 8

@AmbroiseUnly Good find... Cloudron does not support IPv6 only setups yet. But it's coming in the next release (Cloudron 8).

@ccfu it is working now. I guess it needs some time to take effect. Thanks!

What @Dont-Worry said. As long as it' mountable on the server as Cloudron Volume, it should work without a problem. With NAS and network storage, one thing to keep to mind is the flakiness/stability of the network. Apps can behave erratically if the attached storage is not stable.