@oatwalker from those posts, I assume you installed mumble on the side on your Cloudron. While this might work, it could break on future updates as we cannot reliably test such setups. If you are interested, you might want to look into https://cloudron.io/documentation/custom-apps/tutorial/ to see how you could package mumble as a Cloudron app. Also the firewall would have been setup by the platform automatically then.

@girish Just wanted to say that this resolved the issue. Thank you! So to clarify, this was not a Cloudron issue but a simple DNS issue for the SPF records.

This is fixed now, will be part of next release.

@jasonh Ah got it. It looks like adding sender_bcc/recipient_bcc is quite doable. Cloudron uses haraka internally and not postfix and this feature is not available out of the box. We will look into adding this. I will reach out to you by email to double check some of the finer details.

@johnbolt Yes, that's the case. If you have multiple instances, please send us a mail to support@cloudron.io and depending on your use case we can set you up with a discount.

Hi @subven and @nebulon: sorry for not replying sooner. In the middle of the project we decided not to use Ghost (or Cloudron) after all. But you gave me a clearer picture of how it could work if we do with another project. Thanks for the tips.

@d19dotca This is fixed in 4.3 (will be released in the coming days)

Are there any errors reported in the browser console?

@iJoel You can do this by simply concatenating the intermediate and CA cert files into a single cert file. So, in the '.crt' file which you upload to Cloudron, it will have: -----BEGIN CERTIFICATE----- the *.foo.com certificate -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- intermediate cert -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- root cert if any -----END CERTIFICATE----- The ordering of the certs is important above.

@988uh is there any update on this from your side?

Please try again on a fresh Ubuntu install and see if this is reproducible or just some intermediate issue.

Please send an email to support@cloudron.io with the email address you have registered at git.cloudron.io and I will deactivate the 2fa for that one.

@d19dotca That is strange, we will do a bit more testing here (I think atleast one thing to help us narrow this down is you use encrypted backups)

Thanks, investigating this. I suspect the node module is unable to parse the output because of something in the output. I will keep you posted here.

Is there anything which needs solving then or can it be closed? If this is a permissions issue, maybe the package needs to be adjusted?

@girish Oh okay, thank you! My next question was going to be about deleting the snapshot folder, but it was already answered. I appreciate it!

I can reproduce this. Fixed in https://git.cloudron.io/cloudron/box/commit/7cbe60a484cf03c9373c8f57307ad0d9b49a695a . It's a simple change, in case you want apply it locally on your cloudron

@rfg Agree that Cloudron should not accept emails from spoofed sources. We do have code and configuration in place to block this. Let me investigate.

I have added information here on how to change the graph driver using a systemd drop-in - https://cloudron.io/documentation/storage/#docker-image-location . Please use it at your own risk, since as mentioned, we haven't tested with other graph drivers.