Site is not reachable

[privsec]

Hello all, after 124 days 7 hours 47 minutes, my server is no longer reachable via the web browser - it is reachable via putty/SSH.

I typed "reboot" due to the "A system restart is needed" on the initial log in screen. After doing this, I logged back in via SSH and I ran the commands listed here -> https://forum.cloudron.io/topic/5435/can-not-uninstall-nextcloud/7

After this, my website is no longer reachable.

I can not submit a help ticket due to this either, please assist.

@girish

[privsec]

Just tried to ping the site

C:\Users\PC>ping my.site.com

Pinging my.site.com [id.add.loc.209] with 32 bytes of data:
Reply from id.add.loc.209: bytes=32 time=160ms TTL=45
Reply from id.add.loc.209: bytes=32 time=161ms TTL=45
Reply from id.add.loc.209: bytes=32 time=160ms TTL=45
Reply from id.add.loc.209: bytes=32 time=161ms TTL=45

Ping statistics for id.add.loc.209:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 160ms, Maximum = 161ms, Average = 160ms

So the server is reachable online, it seems cloudron is corrupted?

Or something else I am missing?

[privsec]

I have enabled remote support via sudo cloudron-support [--enable-ssh]

[girish]

@privsec are you able to send me the IP address of your server? Maybe via the chat in this forum since email is not working?

[privsec]

@girish Yes, one sec

[girish]

The nginx configs were corrupt.

Aug 06 03:54:24 v2202012134940135659 nginx[10013]: nginx: [emerg] no host in upstream ":80" in /etc/nginx/applications/a0c93a2d-857c-4c7a-b7b7-9858d09c1858.conf:136
Aug 06 03:54:24 v2202012134940135659 systemd[1]: nginx.service: Control process exited, code=exited status=1
Aug 06 03:54:24 v2202012134940135659 systemd[1]: nginx.service: Failed with result 'exit-code'.

And looking into that nginx config, I see:

    location @wellknown-upstream {

        proxy_pass http://:80;

    }

Not sure how the above can happen. It's supposed to be filled up with the container ip...

[girish]

The fix was just to delete those config files and systemctl restart nginx. Then, in Cloudron dashboard, just Repair the app to regenerate those config files.

[jordanurbs]

This post is deleted!

[joseph]

This is a very old issue, please create a separate topic with the details of the problem.