@girish I'm pleased to say that it worked. I had to disable docker and box and reboot, even though I didn't get the exact error you mentioned but something else related to creating the network (duplicate network). I also had to reboot after enabling and restarting box because otherwise the upgrade got stuck, I believe for a similar network creation problem. But once I did that everything worked well and I'm now happily sitting with version 7.6.3 after two subsequent updates. Many thanks for the help with this! Hopefully this thread will be useful for anyone else who might have this issue in future.

Great then we have at least tackled this bug for the upcoming future.

The next version will prompt the user to overwrite if there is a name collision.

Thanks @girish for the quick reply. I'm getting there.

It seems the options --storage-driver=overlay2 makes docker unable to start when the data-root is on a mounted through sftp : adding it through the following error at startup failed to mount overlay: invalid argument storage-driver=overlay2 if I use it with a regular data-root, no errors show up. I guess we should conclude that this makes cloudron not compatible with sftp drive for storing docker images.

Yes you are right, the host has it installed. I tried it from a terminal within one of our apps. There it probably would be overkill.

@inane It seems on some networks, our internal DNS resolver (unbound) does not work. It's not clear why. Is yours a private network or some public VPS provider ?

@JUVOJustin said in Send email with brevo relay: I have a sender configured for my-domain.com, while the server has cloudron01.my-domain.com . How can i solve this? Just to double check - on Cloudron, the relay system requires "domain" level relaying . Meaning, it requires a relay that can send with FROM address like <anything>@domain.com , as opposed to specific-address@domain.com . Can you confirm this? I think the easiest would be to allow changing the "From" domain in case a relay is used, since the sending domain will most likely be handled by the relay provider. You can change the From Email address of an app in the Email section of the app - https://docs.cloudron.io/apps/#mail-from-address . If you want my-domain.com , then add this in the Domains view. It will then appear in the dropdown of the Email domain selector as well. Then, Email -> my-domain.com -> Configure Outbound as brevo.

I have updated the screenshot

Great info @jodiecunningham - do you have more information? Is this an included service in Microsoft365 Azure or cost extra? I did find some services, that are very expensive for a small sized company - and I wasn't sure if that where the right ones.

@alexm said in Spamhouse blacklist: I am kind of struggle to understand is it the problem of OVH or the way Cloudron uses this Spamhous open relays? VPS providers have a block of IP addresses and they cycle these IP addresses across their customers as VMs keep getting created and destroyed. This means that your IP was used by someone else previously and maybe they sent a lot of spam (an unfortunately common situation). When this happens, spam watchlists like SpamHaus place the IP address in their email blocklist . In some cases, people will wholesale block the entire VPS provider IP address range since the VPS provider is not responding to spam appropriately. There is a lot of unknowns here since all this handling is not "transparent" - an email receiver can use all sorts of blocklist providers and unknown criteria to determine if your email is "spam" or not. They might even block emails by domain name etc. Your best bet for reliable email is to sign up and use a relay - https://docs.cloudron.io/email/#relay-outbound-mails . If you don't want to use a relay, you have to be "patient" to give your IP and domain a good reputation . You have to also get your IP/domain whitelisted from the various email block list providers. Most of the email blocklist providers have an online form that you can fill up to prove your reputation.

@chaddieboy Be safe out there tonight!

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

@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