Just a heads up, we will be most likely releasing this next week. Most of the new features are done, just going through the testing cycle.

Had this issue on support couple of times already: https://git.cloudron.io/cloudron/box/issues/610

This was resolved offline - most issues where related to unbound (the internal DNS server) being down. Fixed by System -> restart unbound.

This was a bug in our UI code. This is fixed in 3.5

This is easy to get on Cloudron indeed. Two outstanding issues are:

• Cloudron currently does not allow apps to use port < 1024. DNS requires port 53. This is fixable, I guess.
• Exposing Pi-Hole on port 53 would mean, anyone can access it, not just you. DNS has no auth mechanism afaik. So, I can start using your Pi-Hole server as well as the DNS. Not sure if that is good/bad. Maybe with some firewall rules we can make it so that it is IP locked.

@doomilation Yes, we are working on a way to add external storage in our upcoming release. I will update this post as we have some updates.

@EggEek Looks like there is some bug but I cannot make out what it is. Can you try a different browser to check if this is some UI issue? If it's still broken, can you please enable remote support (Support -> Enable Remote Support) and send us a mail to support@cloudron.io . Thanks!

@amg It seems there are multiple issues here:

• Restore via CLI not working. Can you tell me more what the error is?
• Where are you seeing 'Already Setup'? Is this when installing Cloudron? (But the post starts with 'after update' to 3.4)

Please give us more information to help you out.

@CarbonBee Did I understand correctly that the DNS of cloudron A and Cloudron B are different above?

If so, the behavior is expected (not saying it is correct or even good). Currently, there is no easy way to easily 'migrate' domains - it is only easy to migrate a Cloudron from one server to another provided that all the DNS remains the same.

Can you explain your use case a bit more so we can try to come up with a solution together? I guess you are trying to test your backups? How can we make this work when Cloudron has multiple domains? Once you restore to another server, Cloudron will do the DNS setup of apps automatically and it will end up re-configuring the DNS of the apps to point to this new server.

@robw Sorry for the delayed response, we are just coming back from vacation and catching up on support tickets.

If I understand correctly, the Cloudron server has a different outbound IP than the one it detects. We have a custom endpoint (https://api.cloudron.io/api/v1/helper/public_ip) which helps us detect the IP of a server but I guess this detection goes wrong because of your setup.

To fix/workaround this: In the domain setup wizard, you can simply choose "no-op" as the DNS provider. With this provider, all DNS checks are disabled and as long as the domain somehow is able to resolve and reach your cloudron, it should all work. Another thing is that port 80 needs to be reachable as well for Let's Encrypt to work. If this is not possible, you can select 'Self Signed Certs' in the Advanced section of the domain UI.