out of space - normal process not working.

[roofboard]

@subven said in out of space - normal process not working.:

systemctl restart nginx
Hi, Thanks for the reply.

I just did that, I deleted all files in /etc/nginx/cert/, and /etc/nginx/applications/

Then systemctl restart nginx

And box is running.... everything is running, but cloudron is still down.

when i reboot the server

nginx down and I am back at square 1.

[subven]

@roofboard said in out of space - normal process not working.:

I just did that, I deleted all files in /etc/nginx/cert/, and /etc/nginx/applications/

nginx stuff for Cloudron is at /home/yellowtent/platformdata/nginx/applications Please post your log output from the journalctl command above. Also please restart box with the given command, not nginx.

[roofboard]

@subven
Thanks for the reply. Folowing the instructions.
Here are my commands

root@my:~# cd /home/yellowtent/platformdata/nginx/applications
root@my:/home/yellowtent/platformdata/nginx/applications# ls
default.conf  my.domain.com.conf
root@my:/home/yellowtent/platformdata/nginx/applications# rm *
root@my:/home/yellowtent/platformdata/nginx/applications# systemctl restart box

Below is my log output

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

[subven]

@roofboard please also delete certs under /home/yellowtent/platformdata/nginx/cert/ in addition to the conf at /home/yellowtent/platformdata/nginx/applications/ before restarting box service

Not sure if you are supposed to remove nginx.conf at /home/yellowtent/platformdata/nginx/ so if you touched this file (or the mime.types), this could be an issue. In case you removed nginx.conf and mime.type as well and they are not restored by box, hit me up.

[robi]

Deleting all the certs is a problem I reported recently. There may be a fix, but it's not released yet.

Deleting all the confs is ok as they can regenerate, but not without the one cert for the main cloudron host domain.

See what nginx is looking for? I had to generate that cert manually to get the UI back up.

[roofboard]

@subven
I deleted the files in both the directories, I left the ones in /home/yellowtent/platformdata/nginx alone but inspected them (nothing unusual they are the same as other CL instances. )

then with nginx running I ran systemctl restart box

note - box and nginx were already running.

If i reboot the server nginx will stop running

and all the same my.domain.com never loads always ERR_CONNECTION_RESET

[roofboard]

@robi How do you generate certs manually?

[subven]

@robi hmm I remember I had a similar problem where an stopped app had no cert file which caused nginx to fail at start. I just copied and renamed a random cert to get nginx working at all. The cert for the app I was trying to fix was obviously not right but I was able to run nginx,launch the dashboard, remove the cert from the file system and trigger the renewal process from the UI. Maybe this could work too if you drop something "valid" for the dashboard domain into the nginx cert directory ^^

[roofboard]

@subven @robi
ok. so we are talking about the /home/yellowtent/platformdata/nginx/cert/
cert folder. now i have dummy certs from another CL instance., but which files are needed in that directory? I can get them copied over.

I am guessing maybe... default.cert, and default.key

[subven]

@roofboard [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/domain.com.host.cert" start with the one that brings your nginx down ^^

[roofboard]

@subven

wordwrap!!! the problem was staring me in the face! But I could not see it because i did not scroll to the right...

Thanks for the help!!!!

I took a cert and key file from another server, and renamed the default cert to be whatever the error wanted.
first thedomain.com.cert, then thedomain.com.key. and so-forth until it loaded. It is working now! .