Cloudron Forum

Hi everyone,

I've recently deployed Baserow on an AWS EC2 instance. Cloudron is telling me the PTR record needs to be adjusted. To do so, I've looked at the Cloudron documentation and the AWS documentation for Use reverse DNS for email applications.

I then did the following steps:

1. Created an elastic IP address for my instance
2. Made an A record in my Godaddy DNS for pointing "my" to the newly created elastic IP address
3. Made a reverse DNS record in the EC2 console for the elastic IP address

But I am still getting the PTR error on the Cloudron side.

Any clue what I might be missing?

Thank you for your help

Super interested in the Budibase integration as well!

Hey there,

With a DevOps colleague, we turned off the AWS EC2 instance on which Cloudron (and Baserow) is deployed to see if it would boot back up. It didn't. Both the my.domain.com (Cloudron dashboard) and the data.domain.com (Baserow) remain inaccessible several hours after our test.

Could someone please:

• Explain why this happened (happy to provide more details if need be)?
• Comment on whether Cloudron should reboot automatically or not?
• If not, detail what steps I should take to guarantee the system remains stable even in case of a crash?

Thank you for your help

@girish thx.
So I entered systemctl status box. It said box.service - Cloudron Admin is active. Below it give me the error: Yellowtent : unable to resolve host ip-XXX-XX-XX-XXX: Name or service not known (the IP being my IPv4 address for ens5).

I entered systemctl restart box but nothing happened.

I ran /home/yellowtent/box/setup/start.sh and it seemed to have done what it was supposed to.

I asked again systemctl status box. It said box.service - Cloudron Admin is active. Below it gives me the same error: Yellowtent : unable to resolve host ip-XXX-XX-XX-XXX: Name or service not known (the IP being my IPv4 address for ens5).

The my.domain.com still remains unreachable.

Will be emailing you at support@cloudron.io shortly