@robi is right. @ryan can you send us an email to support@ to move your plan to a free plan. Currently, we have to do this manually i.e move something from a paid plan (even if cancelled) -> free plan.

@d19dotca since the email is forwarded , this info is probably lost. One idea is to look into the bounce mail headers. Maybe there is some message I'd or something we can match.

@drpaneas Just give that redis more memory. The "e1ca318a" is the app id. If you put in the search in the apps view, you will know which app's redis needs a bit more memory. It was reported earlier that pixelfed's redis needs more memory after the update. I guess this is because of update to Redis 5.

@jensbee4 are you able to download this backup using the cli tool?

@mehdi This my friend is a good point, thank you for pulling me out of the tunnel. lol

Amazing! And so we all get a confidence boost with a simple timeout fix! Thanks @girish & everyone who contributed on this thread! Love you all

@guyds said in Single domain, multiple cloudrons?: I suppose each Cloudron needs a unique domain name because of the DNS records that are being created when installing a Cloudron: DKIM, SPF, DMARC? Yes, and also because we need a unique location to access the dashboard. what if the domain that's being used for a Cloudron already has e-mail related DNS records, for example when it's already configured for use with G Suite or Office 365? Will Cloudron modify those records, override them or just ignore them? If you have an existing DMARC, it don't touch it. Otherwise, it will put the default strict DMARC policy. DKIM uses a unique selector domain, so it won't affect other DKIM entries. The SPF is modified with "a: my.<domain.com" into the existing SPF.

@d19dotca Ah, I see this on our server as well. It seems that this is printed for all incoming mails because Haraka tries to transfer mail to Dovecot via TLS (via LMTP). Disabling SSL removes the message. Since the message transfer is internal, it's fine. I have pushed the fix for next release but the message is safe to ignore.

@nebulon Perfect, thank you!

thx! @girish restarting the sftp service helped… on the overview there was no error. in the chrome dev tools /console I get still errors btw: multiple 4040 like: DevTools failed to load SourceMap: Could not load content for URLHIDDENHERE/3rdparty/js/showdown.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE and also angular js error: angular.js:13920 ReferenceError: monaco is not defined

@scooke Thanks, although my doctor would probably disagree. Weekend problems just suck in every way. Thanks for the moral support though!

@cumpal please do not use pictures for text. Images can not be filtered or indexed and adding to that you are excluding blind people from accessing the information.

I had to install 18.04, then install Cloudron 5.5.0, then restore the backed up cloudron, then upgrade it to 6.1.2, then make a backup. Then destroy the 18.04 and install 20.04 instead, then restore the 6.1.2 backup....puhh. Done, working! (Could not restore a 26GB Nextcload app, but no problem, had the files backed up locally) Guess this thread can be marked as solved?

@girish Already solved this problem myself thanks

@nebulon Thank you for the quick response, I'll send a note to support.

@jdaviescoates you should probably use the cifs provider, since then at least the error message would be more obvious when not mounted

@d19dotca To add to this, this is why minio has path style to true. Because it will be a pain for selfhosters to create a subdomain (dns and certs) for every bucket they create. Edit: just looked this up now. In minio, one can set MINIO_DOMAIN to enable vhost style per https://docs.min.io/docs/minio-server-configuration-guide.html . I have to test if this works with Cloudron's domain alias feature.

Tha @d19dotca said in Why does cloudron block ports?: @cumpal Cloudron expects to be the only one running on the server, so for security reasons it locks it down unless needed by Cloudron or any of the apps on it. If you need to modify it, I think you can just update the firewall rules manually in Ubuntu, though I've not done that part myself as no need for it yet. but hopefully that at least explains why it's locked down. You may want to review the Cloudron docs on security features too. @girish said in Why does cloudron block ports?: In addition to what @d19dotca said, you can whitelist extra ports using https://docs.cloudron.io/networking/#whitelist-ports . Please use this at your own risk, we don't recommend installing other software alongside cloudron . Thanks for these replies! I got them working.

This change will be reverted. see https://forum.cloudron.io/topic/4584/issue-with-backups-listings-and-saving-backup-config-in-6-2

@nebulon thank you! worked perfectly fine and is very helpful