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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. App stuck uninstalling - nginx error

App stuck uninstalling - nginx error

Scheduled Pinned Locked Moved Solved Support
nginxreverseproxy
6 Posts 2 Posters 791 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • SupaikuS Offline
      SupaikuS Offline
      Supaiku
      wrote on last edited by girish
      #1

      I'm getting this when trying to uninstall apps:
      Nginx Error: Error reloading nginx: reload exited with code 1 signal null

      how can I fix this or get more info about it?

      girishG 1 Reply Last reply
      0
      • SupaikuS Supaiku

        I'm getting this when trying to uninstall apps:
        Nginx Error: Error reloading nginx: reload exited with code 1 signal null

        how can I fix this or get more info about it?

        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #2

        @Supaiku Can you check journalctl -u nginx for errors?

        SupaikuS 1 Reply Last reply
        0
        • girishG girish marked this topic as a question on
        • girishG girish

          @Supaiku Can you check journalctl -u nginx for errors?

          SupaikuS Offline
          SupaikuS Offline
          Supaiku
          wrote on last edited by Supaiku
          #3

          @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.
          
          SupaikuS 1 Reply Last reply
          0
          • SupaikuS Supaiku

            @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.
            
            SupaikuS Offline
            SupaikuS Offline
            Supaiku
            wrote on last edited by
            #4

            @Supaiku

            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:   }
            
            girishG 1 Reply Last reply
            0
            • SupaikuS Supaiku

              @Supaiku

              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:   }
              
              girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #5

              @Supaiku Strange, that is an invalid line! What is that app 7d024dd6-2dfe-44ca-af5f-f3ccd76540b4 ? To move forward, you can just delete that conf file and restart nginx again.

              SupaikuS 1 Reply Last reply
              0
              • girishG girish

                @Supaiku Strange, that is an invalid line! What is that app 7d024dd6-2dfe-44ca-af5f-f3ccd76540b4 ? To move forward, you can just delete that conf file and restart nginx again.

                SupaikuS Offline
                SupaikuS Offline
                Supaiku
                wrote on last edited by
                #6

                @girish sweet- that worked!

                I saw that's also what you said here:
                https://forum.cloudron.io/topic/5457/site-is-not-reachable/7

                And 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!

                1 Reply Last reply
                1
                • girishG girish has marked this topic as solved on
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                  • Login

                  • Don't have an account? Register

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Bookmarks
                  • Search