Thanks @girish!

I tried to reply via your support email already. The cert on your domain looks valid to me, so please clear your history and cache locally for that domain first.

@girish Just as a quick add-on, if you have Comcast business class, port 25 may be allowed by calling the business support line. Same with ATT.

@doomilation Yes, what you have done should work. You don't have to move out appsdata and platformdata.

Best approach as you already found out is to create multiple VPS on your dedi.

@willywonka You can view the credentials in the Web terminal of the app. Once you open the terminal, you can run a command like below. See https://cloudron.io/developer/addons/ for the meaning of the env vars.

env | grep MYSQL env | grep POSTGRES env | grep MONGO

Is it possible that /mnt/storage/boxdata already exists? If so, please remove it first.

@nebulon a per-app quota would be awesome ! Need feature !

@nebulon Many thanks. You guys are awesome..

Cheers

For info, I had to run systemctl restart box on the system, which brought the apps alive.

BUMP: I resolved this issue. It was a specific container (custom made by me, not supported by cloudron) issue is resolved.

@nebulon Would a simple Cloudron app with just the nginx reverse proxy configuration work?

@micmc Whoops, it seems we missed those mails somehow! I will reply to your email shortly.

Hi, can you send an email to support@cloudron.io with the link produced by running the cloudron-support script on your server?

@murgero Yes, agreed. Starting coming Cloudron 4 release, this will happen automatically as long as the same cloudron.io user registers a cloudron with the same domain name.

From what I understand, the device you are trying to connect from does not support any of the ciphers which Cloudron is requesting. We are following the security guidelines of the following communities:

https://bettercrypto.org/static/applied-crypto-hardening.pdf https://mozilla.github.io/server-side-tls/ssl-config-generator/ https://cipherli.st/ https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html

So we likely won't support outdated or insecure ciphers from the platform side.

Is this still an issue? Otherwise I will close this thread.

This is indeed also a common case to have the email not hosted on Cloudron. However Cloudron will still want to send out emails for this domain. There are two components doing so:

the system as such which would send out with no-reply@domain.com the apps, if they need to send out app specific notifications. In such a case the address is dynamically generated depending on the app and which domain it is installed on

Currently none of those can be changed to use some customer email address to send out as.

Regarding the DMARC issue, just to be sure, did you check the mail status tab in the Cloudron dashboard for this domain? The UI will attempt to provide guidance or show issues with email related DNS records there.