@TheMoodBoardz Does it fail with tgz format also? Not sure how to debug this since it is just crashing with no real logs. If you reach out at support@cloudron.io , we can debug further.

@Supaiku did you manage to get it online atleast? AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.bin.evince at line 32: Could no> The above profile seems to be the buggy one fwiw. Maybe delete it or fix that line.

The code is used while subscribing and once the payment succeeds the credits are applied.

So i found the error, it is because Hetzner close the port 25 by default on new dedicater server, so you just have to ask them to open it. Bisous les copains

I think https://forum.cloudron.io/topic/1660/sympa-mailing-list and https://forum.cloudron.io/topic/6776/mailing-list-feature-basic-moderation are the relevant threads. @andrewwri maybe you can leave a note in the sympa thread as to how you installed sympa and how you are maintaining it. Maybe some notes on your current set up will also help (what is the email server? how is it interfacing with the email server etc). thanks!

I will mark this solved, thanks @3246

@girish Sorry for the delayed response. My server is also hosted in Singapore (by Hostinger). I've noted a couple of seconds delay to open Cloudron's app store but it is definitively back. Thank you again for the support !

no sorry. Just coincidentally having a similar issue with backups, at the same time I think. I can see why you'd think that, I kind of jumped into the conversation.

Ah, thanks! I hadn't seen the app-mail-folders before.

cloudron.io - this is Cloudron's website (the company) console.cloudron.io - this is the place where Cloudron's customers login to manage billing. you cannot manage apps or anything of that sort here yourdomain.com - this is the domain you gave when you installed Cloudron, the software, on your server. IMPORTANT: cloudron the company has no access to your servers. Cloudron the software is entirely selfhosted and only you have access to the server. my.yourdomain.com - this is your server's dashboard. this is where you manage apps and other things my.cloudron.io - this is actually Cloudron the company's, cloudron installation. you should not (and cannot) login here! With this in mind: When attempting to login us assigned IP it would redirect to my.cloudron.io. this cannot ever happen. how would I reach login when IP Changed/DNS is not available If IP changes, go to your DNS and then just change the IP address of my.yourdomain.com manually to the new IP. Are you talking about dynamic IP here? If so, use the Dynamic DNS feature. It will automatically update the DNS with a changing IP. Finally, if DNS itself is not available, I guess you have to use /etc/hosts . See also - https://docs.cloudron.io/troubleshooting/#unreachable-dashboard

Ah ok. I guess, let us know if it happens again!

Thanks, it's solved. No disk wasn't changed. It's running on AWS.

@JOduMonT an email server (without email relays) requires a public IP. There is no way around this. Even if you add a second IP, the second IP will be exposed and one can always access your Cloudron dashboard via that IP address. Just have to put an entry in /etc/hosts on my laptop and point that floating IP to my.domain.com and that's it. I guess you are looking for a way to "sandbox" mail server to a specific IP somehow. We don't have a way to do this in Cloudron. I can move this to Feature Requests. But also, it might be easier to just create another VM and run mail on the other VM? Security wise , this is the easiest and cleanest instead of writing a lot of code to make sure mail server and dashboard despite being on the same server don't step on each other (networking wise).

@taowang note that your IP is actually leaked. If you follow the MX record of your domain, you will find your server IP in the DNS. I think this is what the Cloudflare doc is trying to tell you.

@girish I tried this one, but i get a sad no-go : Error put object cloudron-testfile. Message: Socket timed out without establishing a connection HTTP Code: TimeoutError I'll wait the next update Tx for the patch

@gerard thanks for testing. A fix for this is coming next release. The issue is fairly recent. SpamHaus made some policy change when requests come from IPv6 addresses.

@nichu42 This could be a reason... I think source causes should be outside of Cloudron. Let us know

@jdaviescoates Says me, since www. tells people to expect the main brand website. naked doesn't tell them anything, eg: SaaS apps often use naked for their login, and www. for the marketing site. Check out pretty much any big brand you can think of that ought to know, www.google.com etc. I'm sure I read a deeper article on the whys somewhere, but I was in your shorter is better camp for a long time until I realised there were good reasons for the www. being the destination. Cookies containment from subdomains and use of CDNs are a couple of reasons I remember off the top of my head. I'm sure there's others.

@thoresson yes. If you have a Cloud firewall, you can also whitelist just your IP for port 222.