For me. It's silly. All the guide is out of date. With new created storage box, there isn't sub dir and ssh pub key is not yet allowed in storage box and storage box's pub isn't in my pc known_hosts, I have to add my pub key to storage and run sshfs command once time to get pub key of storage box. So because of new user without subdirectory, the "remote dir path" after colon should be RELATIVE path or empty "" in this case not "/". uxxxxxx@uxxxxxx.your-storagebox.de: /mnt/local/mount/path -o port=23,IdentifyFile=/home/username/.ssh/id_rsa ....

@chaddieboy Be safe out there tonight!

I have a CIFS mounted, but it has fixed itself and appears to work normally now.

@imc67 yeah, the logs are probably not there anymore. One thing is if you go to the Eventlog section of the app, do you see if a backup was ever made?

I can confirm there is this quirk: If an app is stopped and backup was never created, then we don't have backups for this app. Maybe we have to inform the user about this somewhere.

@Neluser It's always appreciated when solutions are posted because eventually someone has a similar or same question. Thank you!

@girish That's right, that's what it says. Thank you for the detailed answer. I've now tried it again and it wasn't actually the DNS cache, but the automatic DNS server that was causing problems. So far everything is working and everything is fixed. Really nice what Cloudron can offer all in one.

Oops, I stand corrected about the login screen translation.

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.