Solved Connection Reset

[SolarSimon]

Hi there,
I have some trouble with my server.
When I want to connect to cloudron my browser says: ERR_CONNECTION_RESET

What I did:

• My Server is running at hetzner, I did a rescale.
• I wanted to use my domain for a different Server, so changed DNS configuration. And returned to original setting.

Since than, I'm having the connection Issue.

What I tried:

• I did not find a solution so I reinstalled cloudron
• I wannted to upload and restore my backups, but apparently it's not that easy
• With snapshot of my Server I returned to the "connection_reset" state

Any suggestions to fix connection?
Or to setup and restore?

[nebulon]

@solarsimon have you checked the various things we mention at https://docs.cloudron.io/troubleshooting/#unreachable-dashboard ?

If those don't help in your case, maybe you can send us a mail to support@cloudron.io with further details about your domain and possibly enable remote SSH for us to debug this directly.

[SolarSimon]

@nebulon said in Connection Reset:

have you checked the various things we mention at https://docs.cloudron.io/troubleshooting/#unreachable-dashboard ?

I did it again with some more fokus.
Result: nginx wasn't active.
I found out port 80 already in use. Apache is installed

I did these steps and cloudron was back online

netstat -tulpn | grep --color :u6e80: 
fuser -k 80/tcp
nginx -t
service nginx start

But after restart of the server, same issue.
Where is apache coming from? I operated this server only by cloudron.
Last action there, I installed git lab.

So now I have to stop apache and start nginx after every reboot.
Should i remove apache?

apt purge apache2

[nebulon]

apache should not be installed. Have you installed anything on the side besides Cloudron on your server? This is generally not supported due to issues like you hit here. Sometimes though the VPS provider images come with extra packages though. Would be good to understand if this is the case for you?

[girish]

@solarsimon said in Connection Reset:

apt purge apache2

yes, in addition, you might have to stop the apache2 service using systemctl stop apache2 and maybe also systemctl disable apache2 for good measure . After that, systemctl restart nginx should have nginx running.

[SolarSimon]

I did a clean installation and restored a backup.
Since than, everything is working fine.
Thanks