@TechoutDev To debug, open the mail logs window. Mail -> Logs button in top right. And then there is another logs button inside it. Keep that browser window open. Then, use the send test mail button - https://docs.cloudron.io/email/#send-test-email . Can you please post what's in the logs?

Hi @girish, ah that fully explains why I cannot interact with the processes running in the container. While your design idea is probably suitable for most cases it won't really work for this specific one. But no harm done, then I will just add a cron service to my app container directly.

I finally managed to get around reproducing and debugging this and it is fixed for next release: https://git.cloudron.io/cloudron/box/-/commit/0cd48bd239b13a6edec04974031ffdfed4688e08

@qwinter Yep, I understood that. But, what DNS settings in the end worked?

@3246 said in Backup mail service and primary MX: I added made sure the record includes "v=spf1 mx..." but it's still showing as erroring in Cloudron Sometimes it takes a while to propagate the change in DNS, so you may need to check it a few hours later.

@scooke said in Newbie Question: Ghost and Nextcloud: Be sure to set up Backup too. I use Scaleway's Block Storage and it gets me 70GB free. +1 And if you need more than that then Heztner Storage Boxes are also good value: https://www.hetzner.com/storage/storage-box

@JLX89 said in Cloudflare + PTR (rDNS) Settings Compatibly: Does anyone know if there is a way around this and enable proxying on example.tld with the mail server at the same location? AFAIK, this is not possible since Cloudflare does not support proxying mail. We are using Vultr for the VPS, so rDNS needs to be setup to reflect the server host (EX: example.tld), if pushing the mail server to mail.example.tld, the rDNS would need to be updated to that. Correct. You have to set the rDNS to the name of the mail server in Vultr.

@fbartels said in Duplicate entry '172.18.17.187' for key 'apps.containerIp': PS: the synapse documentation states that the well known settings are under advanced in the domain settings Fixed!

@niko was there any error restarting cloudron-firewall service or such? This should still work as expected, so maybe you hit a bug somewhere? Also could you share your ports.json config here so we can try to reproduce this? If you don't want to expose your port settings here, you can also send them to support@cloudron.io

Thanks for the info, but we do not use this module, so we are all good.

Don't worry Happens to the best!

@qwinter said in Having a static website side by side with cloudron vs inside cloudron?: What are the downsides of using surfer compared to say the same server without cloudron using nginx or apache My instinct is to rephrase : what are the UPSIDES of using Surfer .... But to answer the question, downside of Surfer is it does one thing serve files. Having a server with full range of facilities opens up possibilities (which you may not actually need/want) but significantly also carries management and maintenance. If 'set and forget' is what you prefer, then Cloudron and Surfer/LAMP is much better than having a traditional self-managed server. And if the question was LAMP on Cloudron vs traditional server, then again the LAMP will almost all of what you would normally do on a normal server without the maintenance headache.

The license was moved, sending an email to support@cloudron.io for this was the correct suggestion ( thanks @robi )

@jdaviescoates Add Hostinger to the list too. I signed up for a basic web hosting plan with them. I created a secondary user account in their admin panel for my developer so he could have access and it didn't work. I contacted support and it took them weeks to get it sorted. Meanwhile, I ended up sharing my main account credentials. I was asked identical questions by different staff (under the same ticket) and I was tossed around like a beach ball in a techno festival. I had better experiences with EIG owned hosts and those guys absolutely s***.

@JOduMonT Hetzner storage box can already be mounted as Samba/CIFS on Cloudron . See also https://docs.cloudron.io/backups/#cifs https://www.infomaniak.com/en/swiss-backup supports S3, so you can add it as S3 compatible.

@nebulon Hi! Yea, everything is working great when hitting the server from outside my network. Your hosts file suggestion is a good one and is something I've done before. I'll dig into that. I seem to remember coming across a bit more of a graceful solution that handles internal/external requests. Thanks for jogging my memory!

@girish OK! Also saw a backup failed notification too for the first time ever, yesterday. I'm really not sure what's happening. I've written to support and let's get on from there. Thanks

@scooke Hi, sorry for the delay. Yeah, @girish was able to solve the problem, which was not a technical one, as usually is the case with these things, heh. The email she uses is an alias, and not <username>@<mydomain>, and she hadn't used it in a while. We're both pretty sure she used to be able to log in with either username only (no '@domain'), or with her aliased email <alias>@<mydomain>, but it seems we're both wrong on this. So I tried to log into her email with <username>@<mydomain> and, lo and behold, it worked. She doesn't use this email at all, so I'm talking to her and seeing if we change her username, since there's only a few apps and email will be the most important one from now on. Thanks everyone for the help!

@girish No I've not patched manually, I have assumed sorry I assumed the latest update was with the CNAME/A-record fix was live. The thing was that my home server has been offline for a while and when I started it up it updated to from v7.0.4 to v7.1.3 then v7.1.3 to v7.1.4. After that the DNS propagation didnt work any longer, as it had done before.