Can you explain better what is the error and what is the current situation ?

I also had some pretty annoying spam, which just wouldn't get marked as spam, despite marking the very same mail previously as spam more than once. In my case tweaking the bayes filter worked very well, but your milage may vary (a lot of spam for me is in German) You can set custom spam assassin rules https://docs.cloudron.io/email/#custom-spam-filtering-rules and there the bayes values like this: score BAYES_999 2.0 score BAYES_99 4.5 But these values may probably have to be adjusted to your case, so I wouldn't bump up the weights too much to avoid marking ham as spam too often. I hope we can improve on that in the future as having to tweak such rules manually is really not a good strategy.

Hah alright, reboot did the trick, sorry for the noise!

@shrey there's some cases where the backup code forgets about older backups. For example, if you switch backup providers (even temporarily). We are trying to improve the whole situation in 9.0 . For a start, with multiple providers, we can track/cleanup more accurately. BTW, if you paste the filename of the backup in your Eventlog, does it find it there? I will look into making this more clearer i.e what is getting deleted and why not getting deleted.

Not sure what you mean with Account ID, but maybe you mean to switch over the subscription from your deleted to your new Cloudron? If so, please send a mail with your cloudron.io details to support@cloudron.io and we can do so.

Removing 2.7 seems to have been seamless. Thank you!

Where are you storing your backups?

I could not let go if it, so I kept digging a bit. I had previously reset the memory limit back to its default, but bumped it to 6gb now for another test. This time the restore of Nextcloud went through. So now everything is operational again (and I also cleaned out some apps that had errors, but I was not using anyways anymore). To get back to a working state I needed to restore each up using a postgres database to the state from before the upgrade to 8.3.0. Else the app would have no data in their databases (Mastodon users and toots gone, Matrix rooms gone, for example).

Ah, I just found the error. For whatever reason the 2fa got disabled for my user and therefore the cli app did not ask for it. My password manager always filled out the 2fa field so I was unaware that it had actually been deactivated.

I will leave this question as unsolved.

@visamp said in New Hetzner Server Installation Best Practices: Do you recommend installing CrowdSec or not? Maybe it's overkill? I had it installed once, looked at pretty graphs for maybe 4–5 days. Then I forgot it, re-setup the server and did not install it again. So, I can not even tell you if it was helpful or not. But what I can say is, no one here really uses crowdsec, nor maintains support for it with cloudron. Good thing is, backup or snapshot, try it, decide for yourself, rollback if it is not to your liking.

Ok thanks. that was helpful! For other people seeking answers: You need to setup new subdomains & app to get one user by app. Example: Tony : tony_n8n.app.mydomain.com Chris : chris_n8n.app.mydomain.com etc

@joseph that was indeed correct. I just generated another token, and it is now working correctly. There was an issue with the Gandi dashboard yesterday. Did not take the time to properly troubleshoot it. Looks like it indeed was a problem on the Gandi side of things. Thanks for your help. Side note: I love your product, and I have been happy paying subscriber for the past few years now. Keep up with the good work

@sweetea got your mail in support, will deal with that there.

Just a quick note here. Route53 supports TLSA records now.

@tzolak yes, no worries

@jdaviescoates said in Cloudron seems to have changed to set-up ?all SPF records instead of ~all - why?: whereas only my newer ones have ?all I checked some domains on my Cloudron and noticed one has -all where all others have ~all. Then I realised that one was a recently transferred domain that was already 'working' and obviously the previous hoster had it like this, Cloudron didn't touch it when "importing" it.

Ahhh. I did not expect that

The posted error logs do not seem to be related as far as I can tell. But anyways if some food solves it, even better, hopefully also stays that way

Not sure what you mean with "redirect" here, but the code checks if the DNS A (and AAAA if you use ipv6 also) are in sync at all configured nameservers for this domain. So basically you just have to make sure that you have setup A records for my.heavendigital.com.br pointing to your server IP. Then after some time, depending on your DNS provider, this should succeed.