Cloudron Forum

Hello, my cloudron server refused to connect via the url which I normally access.

This is the error when I tried to log into the control panel

unexpectedly closed the connection.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_CLOSED

I had not made any changes to it, and thought I would see if a reboot would assist.
It made no difference, so I stopped the server and then started it again to see if that would make a difference.

It did not.

So, I contacted my developer who advised me to log in via ssh and perform some updates but I made a mess of things because I told him it was my runcloud server, not my cloudron server, I must have had a blonde moment being anxious not being able to access my primary invoicing server.

Subsequently I did an update when the information clearly told me not to, which I read after I had done the upgrade. I am normally not this flustered but I didn't know who to contact and it has 3 invoicing systems on there which I can no longer access.

To add insult to injury, I couldn't restart the server because it couldn't find the IP address - the internal one, although it looked like elastic IP had been configured - something is amiss.

So I have something I don't know how to fix.

It's an ec2 instance which I've had running since September 2022 without issue, in fact it's been flawless, but for the life of me this error has got me stumped.

I don't modify things, I had not done any major updates except updating the apps via the panel.

Is it possible to bring it back online?
I haven't got any idea on how to start the process.

When I try to use the sudo reboot option this is what I get -
sudo reboot
sudo: unable to resolve host ip-xxx-xx-x-xx: Name or service not known

However, the IP is connected to the account and is an elastic IP when I look at the aws settings.

I truly do not know why it stopped. I was using it one day, and then went to access the site the next day and I can't find any posts regarding this type of error, support@runcloud.io only does billing.

So I'm wondering - is there any possibility to extract backups from this instance and do a brand new one?

I would be very grateful for someone with wise eyes and mind with cloudron to point me in the right direction because I can't even articulate what I'm meant to ask for to get answers I need.

Thank you

@scooke I use cloudron and runcloud - I have lightspeed and ec2 instances. I made the mistake of when I discussed with my developer I used the word 'runcloud' instaead of 'cloudron'.

I run both - I am running cloudron on an ubuntu ec2 build. This is the one with the issue.

I have located my backups on cloudflare.
I just keep having a brainfart between the words 'runcloud' and 'cloudron'.

The reason I ended up using cloudron was because of issues with laravelle and invoiceninja where due to how runcloud works, it was not possible to get working, so my dev walked me through spinning up an ec2 instance and connecting to cloudron and using the app to build it. It's absolutely fantastic.

I don't know why I keep on getting it mixed up... It must be my left and my other left, but I definitely know what I have built.

Thanks for replying.

I solved the problem -
Purchased another hosting plan from a provider who supports runcloud
Creating a new instance
Imported in all the data from the backups
Redirected the IP addresses after connecting to cloudflare
Works like a charm
Used ChatGPt to walk me through some of the ssh setup
... I learnt one thing... If you are ever doing this, leave things alone for at least 20 minutes before changing something. It was like a perpetual loop of not working and when I left it, came back an hour later, put the same strings in to connect to the cloudflare r2 buckets, it worked like a charm.

I will be honest, I am quite happy I learnt a few more things. A fresh instance of Cloudron was the answer, I don't know why it happened in the first place, given nothing had been changed and one day it was broken after running without issue since Sept 2022, but now I have confidence in fixing things should it occur again.

Backups were really important. Thank you