@whitespace I see that earlier in the thread you said you had no backups. But just wanted to double check, if you had any (even ancient ones) ? The reason is config.php has passwordsalt and secret which is what is used to hash the db entries. https://github.com/nextcloud/server/issues/34780 has some suggestions which may or may not work . As for your question, not a nextcloud expert, but if I had to guess user settings and password will be reset since the data files is only the files.

@girish said in Support for .co.uk Namecheap domain: I have fixed that too. You are a wonder!

It seems the issue here may have been a lot of CPU steal on my VPS, my provider has moved my VPS to a different host server and now it seems to be no longer timing out. Still monitoring, but seems to be the situation.

@robi thx, that was the problem!

yes, support@cloudron.io is the address. For support, this forum is the correct place to ask. Only reach out by email only if private exchange is needed. Thanks!

Sure, I'll write you there.

@girish thank you, I tried it several times and it didn't worked. I tried it a last time and it worked. I don't know why but thank you

I have the solution, VPS is blocked SMTP , now is open now is working

Could Cloudron find some way of partnering with a company which produces routers, or a project which works on wireguard supporting firmware? I think reducing friction to self-hosting Cloudron at home could help Cloudron become more widely used.

Firefox?

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