Super interested in the Budibase integration as well!
gabrielle
Posts
-
Budibase: an open source, no code platform -
Cloudron and Baserow staying down after AWS EC2 simulated crash@girish thx.
So I enteredsystemctl 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
-
Cloudron and Baserow staying down after AWS EC2 simulated crashThank you for your reply
So the instance managed to restart and Docker as well. It looks like it's either Cloudron or Baserow that didn't reboot.
I can SSH into the server.
I doubled checked if my.domain.com resolves correctly and it doesn't.
I checked the status of nginx and it says it's active and running since we restarted the instance.
I don't understand what you mean with "box code"?
I entered: systemctl restart docker but nothing happened...Any clue of what I could be missing?
-
Cloudron and Baserow staying down after AWS EC2 simulated crashHey 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
-
PTR record on AWS EC2@girish Ha ok, makes sense, will try setting up the relay and update the thread. Thx!
-
PTR record on AWS EC2Hi 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:
- Created an elastic IP address for my instance
- Made an A record in my Godaddy DNS for pointing "my" to the newly created elastic IP address
- 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