Can no longer access cloudron ui
-
@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 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 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.
@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 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.
@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.certnothing happens
-
@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 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
-
@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
@falkfyre
You must manually refresh the certificate under “Domains & Certs” -
@falkfyre
You must manually refresh the certificate under “Domains & Certs”@matix131997 How do I go about that with no dashboard?
-
@matix131997 How do I go about that with no dashboard?
@falkfyre
Try again, just to be sure, in another browser, you need to confirm connections to the dashboard the wrong certificate. -
@falkfyre
Try again, just to be sure, in another browser, you need to confirm connections to the dashboard the wrong certificate.@matix131997 Nothing, tried a private window and another browser. This is on a VPS btw
-
@falkfyre
Try again, just to be sure, in another browser, you need to confirm connections to the dashboard the wrong certificate.@matix131997 Is there a cli option?
-
@matix131997 Is there a cli option?
@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
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.@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 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
@falkfyre
Well, it is during this troubleshooting that “proxy” should be disabled -
@falkfyre
Well, it is during this troubleshooting that “proxy” should be disabled@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.
-