Cloudron Forum

I solved the same symptoms by recreating Personal Access Token for Cloudron.
Screenshot 2022-01-13 at 6.18.06 PM.png
Read/Write access under Domains required.
Mine just expired after default set 6 months.

@austinsonger

Regarding Linode and Mail - default is blocked by Linode:
https://www.linode.com/docs/guides/running-a-mail-server/

Sending Email on Linode

In an effort to fight spam, Linode restricts outbound connections on ports 25, 465, and 587 on all Linodes for new accounts created after November 5th, 2019.

If you have a need to send mail from your Linode, we ask that you first configure (1) valid DNS A records and (2) rDNS records for any Linodes that you plan to use to send mail. Then, open a Support ticket from the Linode Manager – we’ll ask you to provide the name of the Linode(s) that will be used for mailing.

Once you’ve completed those steps and provided that information, our Support team will be happy to review your request.

@austinsonger Not that you needed even more confirmations, but I can also confirm that all three links work fine from here in Canada. 🙂

@austinsonger this may happen if the server is a bit overloaded or if the disk I/O is slow. The latter can be quickly checked with hdparm -Tt /dev/<your-root-disk-partition>.

Otherwise the blog seems to be up and running fine by now?

Hi @austinsonger is there anything in the app logs regarding that error?

I am not an expert on AWS, but aren't AWS instances only CPU+RAM ? I thought the disk does not resize. This is for EC2 instances though. Are you using lightsail by any chance?

Yup. This makes no sense.

9bafe7ee-807e-4e2a-ae5d-bbf0b94cf89e-image.png

@girish I was actually going to post this before too... that trailing slash is important. However, this behaviour only seems to impact the managed app. The unmanaged app doesn't require that trailing slash. Any ideas why these are different?

@austinsonger Is the server also hosted in Azure? PTR records are not part of your DNS zone. They should instead be set from wherever your server is hosted (i.e whoever owns the IP address of the server) It seem Azure does not have a UI to set PTR records but you have to use the CLI - https://docs.microsoft.com/en-us/azure/dns/dns-reverse-dns-for-azure-services . What you are trying to do is https://docs.microsoft.com/en-us/azure/dns/dns-reverse-dns-hosting I think, this is not what we want. Quite confusing from Azure.

Tagging @derek since he knows Azure stuff.

@mehdi Kinda CPU intense and slow though, when comparing to Wireguard at-least.