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

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

Thank you, @gofaniyi and @girish!
Now everything works.

I will mark this as solved since it was fixed with the update (3.4.3).

Great, thanks!

This is a UI bug in our current release (caused by an update to fontawesome..). You can fix it by doing this:

Open the browser console (firefox, chrome, safari) in the settings page. Run this command angular.element(document.getElementsByClassName('content')).scope().cloudronNameChange.show()

This will open a dialog that will let you set the name.

Some other elements are missing as well in the profile page. For that, run this:

angular.element(document.getElementsByClassName('content')).scope().displayNameChange.show() angular.element(document.getElementsByClassName('content')).scope().emailchange.show() angular.element(document.getElementsByClassName('content')).scope().passwordchange.show()

We will push an update next week.

Yep, thanks. it worked.

Can you check if the backup format is correct (i.e tgz or rsync) when you restore from the backups? The logs are in journalctl -u box -a.

I believe @scooke already got this sorted out.

The solution is to just start over with a fresh Ubuntu install and installing Cloudron. Another important thing to remember is to provide the correct version as part of the installation. It must be ./cloudron-setup --provider generic --version <version>. The version field is in the backup id.

I will mark this as solved, since it's unlikely we will start supporting another OS. Supporting two ubuntu versions is really hard as-is.

@thisiscowboy does this issue persist with the current mailtrain app package?

Just to conclude this thread. Mostly restarting the mail container will bring back the email server. As mentioned by @alexy this is done via docker restart mail

I will mark this thread as "solved", since it is quite old. If this issue is still there, please post a reply.

The wildcard dns would cover that just fine, so no need to take further action at the moment. Eventually during an update the box service will be anyways restarted.

Just for completeness, systemctl restart box requires root capabilities, so it has to run either as root user or through sudo

Is this still an issue? If not, was there a solution?

@tereensio is this issue resolved for you by now?

@tbroady do you have any update on this? Can we mark this as "solved"?