@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.
falkfyre
Posts
-
Can no longer access cloudron ui -
Can no longer access cloudron ui@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
-
Can no longer access cloudron ui@matix131997 Is there a cli option?
-
Can no longer access cloudron ui@matix131997 Nothing, tried a private window and another browser. This is on a VPS btw
-
Can no longer access cloudron ui@matix131997 How do I go about that with no dashboard?
-
Can no longer access cloudron ui@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
-
Can no longer access cloudron ui -
Can no longer access cloudron ui@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
-
Can no longer access cloudron ui@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.
-
Can no longer access cloudron ui@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
-
Can no longer access cloudron ui@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. -
Can no longer access cloudron ui@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:~#
-
Can no longer access cloudron uiAll 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
-
OpenVPN - Setting admin user gives admin to everyone.@girish Awesome! That got it. Thanks. The first time I tried it it didn't take after the reboot but I added back in the " " marks and it worked as expected. Thank you so much. And again for the quick response!
-
OpenVPN - Setting admin user gives admin to everyone.Maybe a syntax issue on my end but I uncommented the admins= line and set an admin name but every user still has access to the admin settings. I've tested with a few different user accounts. Logged out logged back in but they can change network, DNS and client to client. When I do I can see it changing globally in openvpn.conf. Am I missing something?
Current Config:
[roles] # Restart the app and re-login for role change to take effect admins="username" (changed to protect the innocent)
Tried removing "" from username but I get the same behavior. I have reboot with every change I've tried.