@necrevistonnezr True, but imapfilter ( or another workaround ) is here today for you to achieve what you want. Beats waiting for the feature you're asking for which might be available sometime soon, later .... or never.

@girish
thanks, i will go with 4.3.

Ok, I solved it. I had to delete all my DNS settings that previously existed and then reset them. Once I did this within milliseconds Cloudron started working.

Whew, I was sweating bullets there for a minute.

@onlybro thanks for the heads up on this. I think I understand the reason for that recommendation. But to understand this in the Cloudron context, once the box process starts up, we create a mysql connection pool. This is never destroyed and as long as the box process is up and running, the name resolving is only done during startup once. So I think we are good as is on this one.

I would actually be more curious about the memory settings you mentioned, that is probably more worthwhile understanding.

@d19dotca Okay, that is a bit confusing, but I will only be able to figure it out once I try it.

I appreciate everyone's help and responses.

@mastadamus right, the spamlists won't work if those lookups get blocked. Currently, if the lookups fail, the mail server will simply go ahead and try to detect spam via spamassassin. It's just one of the metrics for spam detection. I guess it's fine if it's working OK for you without it .

@girish yep, it loads, awesome, thank you👍 😊

@fbartels no fts, on some servers there aren't even any mailboxes

@girish I know that, but since I'm not using mail in most of those cases, I would rather want to find out what spam-methods create the memory spike instead of allowing more attempts 😉

@xevotech What are the contents of /app/data/php.ini ? It seems there is some syntax error. Note that you have to restart the app for the php.ini changes to take effect.

@timconsidine Also good to point out is if the plan is to just use a personal google account's SMTP settings it will be severely rate limited.

Agreed, I think we should open up a separate app request for this minio console.

Community fork in 3… 2… 1…?

@d19dotca Sadly, they do match. I'm guessing it's something with my current setup that's acting funny. I'll ignore it for now since I plan on migrating either to the new Contabo server that I got or upgrading my current one at DO to Ubuntu 20.04. I just thought it was a wrong setting on my part.

Thank you for looking into this and for sharing the custom spam rules! I know you've put a lot of time into that 👍

2443c4d7-ec13-4149-add3-28e1e7ad48ed-image.png

@scooke Maybe the redis went corrupt. Looks like it is just a cache for the app, maybe you can try clearing it:

First make a note of the app id. If you do docker stop redis-<appid> rm /home/yellowtent/platformdata/redis/<appid>/dump.rdb. This clears the previous redis database. docker start redis-<appid> Restart the app as well to re-establish redis connection

@girish I'm not sure. It is intended to support image and other media uploads, so perhaps they're looking at long term consumption with such media. There is an open issue about it, and user diamkil seems to be pursuing the bundled-minio image strategy. The reddit thread mentions local storage throughout.

The current storage provider implementation seems to serve files by providing the client an s3-style signed url. Perhaps a new provider could be written that provides a file url that just points to the server itself, I guess requests would be authenticated by the usual domain cookies.

@girish said in DNS CNAME and Cloudron Redirect for WWW:

roundbear.org

Thanks - that'll teach me to test things simultaneously! Fixed.

Solution:

set cname on cloudflare to www / baredomain.com set redirection on the app to add www

Fixed now 😄

@d19dotca Yes, I think you're right, thank you.
I need to look into that.
Or move some long term storage files ("archive") into Minio.
That might just be moving the problem, but dividing the problem might be a partial solution.

@humptydumpty Yes, correct. Server restart won't fix the issue, have to restart the service explicitly (since it copies over certs).

@ethanxrosen No worries 🙂 I hit the same problem a few months ago (however, I ended up basically never using CouchPotato to download stuff directly, instead basically only using it for post-processing, as it's not that good at it, and it's much less useful for movies than for TV shows)

This caveat shoud however be noted in the CouchPotato documentation https://docs.cloudron.io/apps/couchpotato/ . @girish maybe you can add a line there that says that to use CouchPotato with Transmission, one has to use Black-hole?

@nebulon Yep, thank you, confirmed it reset itself.
Took >24 hours for recalculation but it is sorted 👍

Right, only one path was implemented since I wanted a use case for having multiple ones before implementing it. Looks like I got a use case now...

@girish That worked, thank you!

@girish that fixed the issue. Thanks!

Thanks, Girish. I'm happy to test it once you've got it running if that helps?

@girish Ubuntu 16.04.4 LTS, ah I just spotted this article: https://docs.cloudron.io/guides/upgrade-ubuntu-20/ will try upgrading and see if the issue persists

I too need to migrate 6 highly customised Wordpress sites built with 6 different themes/ pagebuilders from Cloudways to Cloudron. Petrified!!!

A guide on how to migrate themes + plugins + content + media + javascript/css customisations + settings + Google Analytics will be highly appreciated!

Hi @subtlecourage,

is that all the same domain for these error messages? when you manually look up the mx records of these domains, do they exist? if you do a portscan on one of the mx hosts, does something listen on port 25?

We haven't worked out the details around subscription for multihost, however you still can just go ahead as you mentioned. Anyways you can migrate apps from one Cloudron to another, mostly this works well as long as the usernames are consistent (we try to setup most apps to use the username as the unique identifier)

@derin If email works, you can just click Reset password in the login page and you will get an email with the reset link. If email is wrong or does not work, you can SSH into the server and run cloudron-support --admin-login. This will give you a one time use password (will also print the username to use). You can then go to Profile and change the password. Note that you have to run the command again to get a new password when changing the password.