App stuck uninstalling - nginx error
Solved
Support
-
-
@girish said in App stuck uninstalling - nginx error:
journalctl -u nginx
it says:
Dec 04 15:33:04 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Start request repeated too quickly. Dec 04 15:33:04 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Failed with result 'exit-code'. Dec 04 15:33:04 ashevillains-cloudron-amd-nyc3-01 systemd[1]: Failed to start nginx - high performance web server. Dec 04 15:39:23 ashevillains-cloudron-amd-nyc3-01 systemd[1]: Starting nginx - high performance web server... Dec 04 15:39:23 ashevillains-cloudron-amd-nyc3-01 nginx[21276]: nginx: [emerg] no host in upstream ":8008" in /etc/nginx/applications/7d024dd6-2dfe-44ca-af5f-f3ccd76540b4.conf:137 Dec 04 15:39:23 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE Dec 04 15:39:23 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Failed with result 'exit-code'. Dec 04 15:39:23 ashevillains-cloudron-amd-nyc3-01 systemd[1]: Failed to start nginx - high performance web server. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 1. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: Stopped nginx - high performance web server. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: Starting nginx - high performance web server... Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 nginx[21306]: nginx: [emerg] no host in upstream ":8008" in /etc/nginx/applications/7d024dd6-2dfe-44ca-af5f-f3ccd76540b4.conf:137 Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Failed with result 'exit-code'. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: Failed to start nginx - high performance web server. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 2. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: Stopped nginx - high performance web server. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: Starting nginx - high performance web server... Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 nginx[21324]: nginx: [emerg] no host in upstream ":8008" in /etc/nginx/applications/7d024dd6-2dfe-44ca-af5f-f3ccd76540b4.conf:137 Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Failed with result 'exit-code'. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: Failed to start nginx - high performance web server. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 3. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: Stopped nginx - high performance web server. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: Starting nginx - high performance web server... Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 nginx[21336]: nginx: [emerg] no host in upstream ":8008" in /etc/nginx/applications/7d024dd6-2dfe-44ca-af5f-f3ccd76540b4.conf:137 Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Failed with result 'exit-code'. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: Failed to start nginx - high performance web server. Dec 04 15:39:24 ashevillains-cloudron-amd-nyc3-01 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 4.
-
nginx -t nginx: [emerg] no host in upstream ":8008" in /etc/nginx/applications/7d024dd6-2dfe-44ca-af5f-f3ccd76540b4.conf:137 nginx: configuration file /etc/nginx/nginx.conf test failed
on line 137:
135: location @wellknown-upstream { 136: 137: proxy_pass http://:8008; 138: 139: }
-
@girish sweet- that worked!
I saw that's also what you said here:
https://forum.cloudron.io/topic/5457/site-is-not-reachable/7And is basically what's described in the troubleshooting as well.
At first this was just an issue with the uninstalled containers, but then when I restarted for a cloudron update it took down the whole thing, which made me think ngnix really was broken
Thank you!
-