Glad you sorted it out. And interesting that your second attempt was 202 which is also what you picked as a default alternative to 22

@dsp76 indeed, thanks for reporting. The error message should read Hetzner instead of OVH when you select Hetzner. I have fixed this for the next release.

@laurent said in OVH no longer supported as DNS provider ??: It may come from an adblocker I installed in Safari I guess

@subven I rebooted many times and unbound never came back so this isn't necessarily true. It wasn't until coming across this post that I was able to solve by repeatedly trying to start unbound times about 3 tries. Thank you to OP and @girish for the solution!

Note that depending on the app, you might have to query a different port i.e the port it is listening on. # curl -L http://12aded8a-8c78-4b6c-bdbe-2d549b1c2eb5:3000 | wc -c % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 11 0 11 0 0 1412 0 --:--:-- --:--:-- --:--:-- 1571 100 11 0 11 0 0 417 0 --:--:-- --:--:-- --:--:-- 417 100 143k 100 143k 0 0 1464k 0 --:--:-- --:--:-- --:--:-- 1464k 147314 Directus listens on port 8055 and n8n on port 5678

For the record, the resolution was that I had two accounts, one an admin and one a superadmin (both with a similar username). I believe that my logging into an app as the admin caused my current account in Cloudron to also become admin. This hid the "Configure" button in the Backup section--while admins can see the backup settings, only the superadmin can change them. Logging out of the admin account immediately gave me access to superadmin again.

also read this

@vjvanjungg yep, they use minified version of Ubuntu, so first of all you have to use their Ubuntu images to install a full version, see https://forum.cloudron.io/topic/10097/cloudron-install-error-dpkg-error/6?_=1696615795636 Also, I asked them about this on Twitter and they said: I expect the Cloudron install script to work if you run the command "chattr -i /etc/resolv.conf" before starting it https://twitter.com/netcup/status/1735265955364720757 So perhaps try that first and let us know if it does indeed work?

Yeah it does, but for a short while it didn't. I use the gps.domain.nz for traccar and thats what it said it was incorrectly pointed at instead of my.domain.nz, but it resolved itself and has only happened the one time.

Note that when you restore on IP2, Cloudron will adjust the DNS of the apps to point to IP2. It can do this only if you use one of the programmatic DNS providers. If you use manual/wildcard DNS provider, you have to change the IP manually yourself.

This is fixed in the latest release 7.6.2

This means that either your cloudron.io credentials are wrong if you are in the login mode of that form or if you are signing up, the email may already be known? To rule out one part here, can you just log into https://console.cloudron.io to verify the account credentials are correct?

Thank you @laurent I'll try something like that.

This has not been tested by us at least and given that 23.04 is not an LTS there is probably no big rush if at all to support it.

@robi said in How to setup cloudron with Epik domains?: It's in the docs, or just try it to see what it asks for. Hey, thanks! The wildcard option worked... or so it seems!

Cloudron is itself a reverse proxy, so you have an additional one in front of it, which means you need to configure it as such. Many guides online for that. Another options is to use the Cloudron install and server as a more friendly reverse proxy for your entire network. For any other systems or domains you just set up a proxy app within cloudron that further redirects things properly on your private network.

Thank you for your response.

Responded in support ticket.

I think your solution for my "bad reputation OVH server IP" problem did the truck. Thanks @nebulon

Thanks again, and for sharing the details!