@Grienauer I think Services -> Mail -> Restart. This updates the mail server certs. Can you check if it works after that?

@robi yeah, I tried to cat / tail it, was unicode garbage. me thinks corrupted

@interface as long as your Cloudron dashboard is reachable you can perform all this from the UI. If your IP has changed by now for the dashboard as well, then initially set your current IP manually for your my.example.com dashboard domain to reach that again.

@shan 7.3.3 I believe.

@squareclouds I can asure you that your deliverability rate will not improve if you send through a selfhosted SMTP relay. Also sending from your Cloudrons SMTP won't be better (in most cases) other then your providers mail server. Ugly truth is that email besides the "big brands" is kinda broken. I pay 11$ ransom to mailjet every month to get my ~2500 mails/month out

@jaschaezra We used to have that link in the docs but for some reason it got removed from mastodon upstream, which resulted in a broken link in our docs Note the link I posted is actually in some fork and not upstream!

@opensourced you can update to 7.3.2 which has the fix for this. Settings -> Check For Updates. It will say Unstable but it should be stable (there are a few bugs outstanding but nothing major).

@harrowsmith can you run docker network inspect cloudron to see if the network it tries to bind on is actually created?

So all the pages are now dynamically fetching app info and are thus always current.

@thoresson yes, exactly.

@nebulon said in Confused about a failed backup being listed in backups: @jdaviescoates if you hover over the 5 hours ago you should see the exact time to validate this. It shows 05:54:18 so I guess your theory was correct given the logs I pasted above about the failed backup show 04:00:01 - thanks!

@jdaviescoates said in Backing up multiple Cloudrons to the same backup destination?: And just to be double clear, having different prefixs results in different paths, right? yes!

This is fixed now, thanks for reporting.

@girish many thanks !

@scooke thankfully not. he did trash some websites, maybe not realizing how easy it is to restore a backup, but he wasn't ambitious enough to try and jack my server

@RazielKanos said in can't send mails to gmail: The IP you're using to send mail is not authorized to send email directly to our servers. Please use the SMTP relay at your service provider instead. Learn more at https://support.google.com/mail/?p=NotAuthorizedError f13-20020a05600c4e8d00b003c6f97b761esi8416758wmq.104 - gsmtp Oh, I missed this. See https://support.google.com/mail/answer/10336?hl=en . Basically, google does not like your IP. Maybe they have blocked the whole IP range of your VPS provider . You have to use a relay - https://docs.cloudron.io/email/#relay-outbound-mails

@blacksunmastodon Delete the config files under /home/yellowtent/platformdata/nginx/applications and systemctl restart nginx. Does that bring up nginx?

@girish I can confirm. I had "Error : Task Error - Task 4237 stopped" and I did what you said, and it restore from backup normally. All my updates were stuck with the same error. Coincidentally, Contabo was having maintenance before, and every time they did a repair Cloudron acted a bit weird. I suspect it might have to do with the server hosting...

Hi there, I just double checked our support spam folder there and I can't find any related mails. Do you get bounces when sending mails? For your initial issue, you can also send a mail to sales@cloudron.io directly with your two email addresses used for those subscriptions, I should then be able to refund accordingly. Please also let us know if and which subscription you want to keep.

@jdaviescoates The first one is from redis, it can be ignored. The second is the healtheck bot. It appears when the app is not up yet. That can be ignored as well. The final one is because the apache config has ServerName unset. Which app is this? Setting the ServerName to some dummy name makes it go away.