Can no longer access cloudron ui

falkfyre

All of the sudden I can't connect to cloudron ui. Email works and I continue to get error notifications about backups but can't access. SSHd in and nginx.service can't start.

nginx -f

nginx: [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/_.imitz.cc.cert": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/home/yellowtent/platformdata/nginx/cert/_.imitz.cc.cert, r) error:10000080:BIO routines::no such file)
nginx: configuration file /etc/nginx/nginx.conf test failed

systemctl status nginx.service

nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset:>
    Drop-In: /etc/systemd/system/nginx.service.d
             └─cloudron.conf
     Active: failed (Result: exit-code) since Sun 2024-10-06 21:28:53 UTC; 6min>
       Docs: man:nginx(8)
    Process: 3185 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_proce>
        CPU: 22ms

Oct 06 21:28:52 localhost systemd[1]: nginx.service: Control process exited, code=exit, status=1/FAILURE
Oct 06 21:28:52 localhost systemd[1]: nginx.service: Failed with result 'exit-code'
Oct 06 21:28:52 localhost systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Oct 06 21:28:53 localhost systemd[1]: nginx.service: Scheduled restart job, restart job, restart counter is at 5.
Oct 06 21:28:53 localhost systemd[1]: Stopped A high performance web server and a reverse proxy server
Oct 06 21:28:53 localhost systemd[1]: nginx.service: Start request repeated too quickly.
Oct 06 21:28:53 localhost systemd[1]: nginx.service: Failed with result 'exit-code'
Oct 06 21:28:53 localhost systemd[1]: Failed to start A high performance web server and a reverse proxy server.

root@localhost:~# /home/yellowtent/box/setup/start.sh
2024-10-06T21:51:20 ==> start: Cloudron Start
media:x:500:
2024-10-06T21:51:20 ==> start: Configuring docker
Synchronizing state of apparmor.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable apparmor
2024-10-06T21:51:22 ==> start: Ensuring directories
2024-10-06T21:51:22 ==> start: Configuring journald
2024-10-06T21:51:22 ==> start: Setting up unbound
2024-10-06T21:51:22 ==> start: Adding systemd services
Synchronizing state of unbound.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable unbound
Synchronizing state of cron.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable cron
2024-10-06T21:51:28 ==> start: Configuring sudoers
2024-10-06T21:51:28 ==> start: Configuring collectd
2024-10-06T21:51:28 ==> start: Configuring sysctl
2024-10-06T21:51:28 ==> start: Configuring logrotate
2024-10-06T21:51:28 ==> start: Adding motd message for admins
2024-10-06T21:51:28 ==> start: Configuring 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.

Not sure how to proceed

girish

@falkfyre this was a bug in an old version of Cloudron. If you run cloudron-support --troubleshoot it will remove the bad nginx config. The troubleshoot tool still requires a recent version of Cloudron though.

To fix manually:

cd /etc/nginx
grep -ir _.imitz.cc.cert
The above will a nginx conf file. Delete this file.
systemctl restart nginx
Then, https://docs.cloudron.io/troubleshooting/#failed-upgrade (just run the start.sh script)

falkfyre

@girish Now I get

root@localhost:/etc/nginx# 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:/etc/nginx# systemctl status nginx.service
× nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset:>
    Drop-In: /etc/systemd/system/nginx.service.d
             └─cloudron.conf
     Active: failed (Result: exit-code) since Mon 2024-10-07 14:52:21 UTC; 31s >
       Docs: man:nginx(8)
    Process: 4306 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_proce>
        CPU: 23ms

Oct 07 14:52:21 localhost systemd[1]: nginx.service: Control process exited, co>
Oct 07 14:52:21 localhost systemd[1]: nginx.service: Failed with result 'exit-c>
Oct 07 14:52:21 localhost systemd[1]: Failed to start A high performance web se>
Oct 07 14:52:21 localhost systemd[1]: nginx.service: Scheduled restart job, res>
Oct 07 14:52:21 localhost systemd[1]: Stopped A high performance web server and>
Oct 07 14:52:21 localhost systemd[1]: nginx.service: Start request repeated too>
Oct 07 14:52:21 localhost systemd[1]: nginx.service: Failed with result 'exit-c>
Oct 07 14:52:21 localhost systemd[1]: Failed to start A high performance web se>
lines 1-17/17 (END)

root@localhost:~# /home/yellowtent/box/setup/start.sh
2024-10-07T14:55:46 ==> start: Cloudron Start
media:x:500:
2024-10-07T14:55:46 ==> start: Configuring docker
Synchronizing state of apparmor.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable apparmor
2024-10-07T14:55:48 ==> start: Ensuring directories
2024-10-07T14:55:48 ==> start: Configuring journald
2024-10-07T14:55:48 ==> start: Setting up unbound
2024-10-07T14:55:48 ==> start: Adding systemd services
Synchronizing state of unbound.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable unbound
Synchronizing state of cron.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable cron
2024-10-07T14:55:53 ==> start: Configuring sudoers
2024-10-07T14:55:53 ==> start: Configuring collectd
2024-10-07T14:55:54 ==> start: Configuring sysctl
2024-10-07T14:55:54 ==> start: Configuring logrotate
2024-10-07T14:55:54 ==> start: Adding motd message for admins
2024-10-07T14:55:54 ==> start: Configuring 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:~#

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.

Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Cloudron Forum

Can no longer access cloudron ui