Cloudron Forum

(I think workers/reports/config/default.toml also needs to be editable to allow access to a MySQL user)

Ahh great! Thanks - There seems to be some issues with report running through, it always fails with the below message. Any idea why this might be?

WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
ERR! reports connect ECONNREFUSED 127.0.0.1:3306

Any way of enabling Mailtrain reports? It enables list exports amongst other things which are incredibly useful for list management. The following lines need to be added in config/production.toml but we don't seem to be able to edit the filesystem:

[reports]
enabled=true

Hello! Sorry - yes inbound 80 is open. results of journalctl:

No journal files were found.

@girish Sure! I'm on 2.0.1, only one app installed - It's been failing for both the main app domain and the config subdomain for about a week now

Hello! Is anyone else having issues with Lets Encrypt failing SSL certs? Nothings been touched on the domain or Cloudron setup since initial install and I'm getting the below mail daily:

Dear Cloudron Admin,

The certificate for <domain name> could not be renewed.

The Cloudron will attempt to renew the certificate every 12 hours
until the certificate expires (at which point it will switch to
using the fallback certificate).

The error was:

Unexpected status: invalid

Powered by https://cloudron.io

Sent at: Mon, 16 Apr 2018 11:00:50 GMT