Can no longer access cloudron ui

[girish]

@falkfyre nginx is still not working (for some reason). What are the nginx logs saying? These are sometimes in journalctl -u nginx -fa and sometimes in /var/log/nginx/error.log

[falkfyre]

@girish root@localhost:~# journalctl -u nginx -fa
Oct 07 14:55:55 localhost nginx[5267]: nginx: [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/imit.tech.cert": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/home/yellowtent/platformdata/nginx/cert/imit.tech.cert, r) error:10000080:BIO routines::no such file)
Oct 07 14:55:55 localhost nginx[5267]: nginx: configuration file /etc/nginx/nginx.conf test failed
Oct 07 14:55:55 localhost systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Oct 07 14:55:55 localhost systemd[1]: nginx.service: Failed with result 'exit-code'.
Oct 07 14:55:55 localhost systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Oct 07 14:55:55 localhost systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
Oct 07 14:55:55 localhost systemd[1]: Stopped A high performance web server and a reverse proxy server.
Oct 07 14:55:55 localhost systemd[1]: nginx.service: Start request repeated too quickly.
Oct 07 14:55:55 localhost systemd[1]: nginx.service: Failed with result 'exit-code'.
Oct 07 14:55:55 localhost systemd[1]: Failed to start A high performance web server and a reverse proxy server.

[falkfyre]

@girish Do I just need to go through and delete all of the config file like the first thing you said. Has me a bit worried and I have a number of domains in there

[girish]

@falkfyre yes, correct. deleting the nginx configs and even the certs is totally safe, Cloudron can re-create the configs with no data loss.

Once nginx is online, access the dashboard. Then, just go into each app and do "Repair" . This will regenerate the nginx configuration.

[falkfyre]

@girish Now I'm just getting

root@localhost:~# systemctl restart nginx
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xeu nginx.service" for details.
root@localhost:~# 

root@localhost:~# journalctl -u nginx -fa
Oct 07 15:51:29 localhost systemd[1]: nginx.service: Failed with result 'exit-code'.
Oct 07 15:51:29 localhost systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Oct 07 15:51:29 localhost systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
Oct 07 15:51:29 localhost systemd[1]: Stopped A high performance web server and a reverse proxy server.
Oct 07 15:51:29 localhost systemd[1]: nginx.service: Start request repeated too quickly.
Oct 07 15:51:29 localhost systemd[1]: nginx.service: Failed with result 'exit-code'.
Oct 07 15:51:29 localhost systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Oct 07 15:51:33 localhost systemd[1]: nginx.service: Start request repeated too quickly.
Oct 07 15:51:33 localhost systemd[1]: nginx.service: Failed with result 'exit-code'.
Oct 07 15:51:33 localhost systemd[1]: Failed to start A high performance web server and a reverse proxy server.

[falkfyre]

@girish root@localhost:~# journalctl -u nginx -fa
Oct 07 15:57:27 localhost nginx[4359]: nginx: [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/imit.tech.cert": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/home/yellowtent/platformdata/nginx/cert/imit.tech.cert, r) error:10000080:BIO routines::no such file)
Oct 07 15:57:27 localhost nginx[4359]: nginx: configuration file /etc/nginx/nginx.conf test failed
Oct 07 15:57:27 localhost systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Oct 07 15:57:27 localhost systemd[1]: nginx.service: Failed with result 'exit-code'.
Oct 07 15:57:27 localhost systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Oct 07 15:57:27 localhost systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
Oct 07 15:57:27 localhost systemd[1]: Stopped A high performance web server and a reverse proxy server.
Oct 07 15:57:27 localhost systemd[1]: nginx.service: Start request repeated too quickly.
Oct 07 15:57:27 localhost systemd[1]: nginx.service: Failed with result 'exit-code'.
Oct 07 15:57:27 localhost systemd[1]: Failed to start A high performance web server and a reverse proxy server.

When I do
cd /etc/nginx
grep -ir _.imit.tech.cert

nothing happens

[falkfyre]

@girish Ah, got it to start. No dashboard but I'll run the start.sh

[falkfyre]

@girish Ok, now I have a new issue. I'm am getting an invalid ssl cert error when trying to access the dashboard and it doesn't seem to be renewing

[matix131997]

@falkfyre
You must manually refresh the certificate under “Domains & Certs”

https://docs.cloudron.io/certificates/#manual-renewal

[falkfyre]

@matix131997 How do I go about that with no dashboard?

[matix131997]

@falkfyre
Try again, just to be sure, in another browser, you need to confirm connections to the dashboard the wrong certificate.

[falkfyre]

@matix131997 Nothing, tried a private window and another browser. This is on a VPS btw

[falkfyre]

@matix131997 Is there a cli option?

[matix131997]

@falkfyre
How do you connect and have a message about an erroneous certificate. At the bottom you have a button “Advanced” and there you have a button to go to the page.

[falkfyre]

@matix131997 Proxied through cloudflare. There is no advanced option. It isn't like how a self signed or local shows up.

my.imit.tech

I'll try turning off proxy option in cloudflare

[matix131997]

@falkfyre
Well, it is during this troubleshooting that “proxy” should be disabled

[falkfyre]

@matix131997 Didn't cross my mind. this is a new issue. Hence the reason I mentioned it could have been part of the problem that just came up a minute before.

[girish]

@falkfyre so did it work out?