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


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Problem with NGINX when installing/restarting any app

    Support
    nginx
    3
    5
    244
    Loading More Posts
    • 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.
    • R
      revck last edited by girish

      Hello,

      Initially Cloudron was working fine, then I added volumes to it and applications, and problems arose.
      Cloudron is running inside vmware workstation pro, with volumes mounted.
      Volumes are accessible by command line, and on Cloudron Web GUI they show as a green circle, but when I click 'open file manager' not all show content, even if I wait. I believe the errors below started presenting after adding volume, but I do not know if it is coincidence or it is linked, so let's hold our thoughts for now.

      Adding/Starting/Installing any app now gives me NGINX errors. If I restart Cloudron, it seems for a bit it allows me to install those apps that were failing.
      Restarting Cloudron gives NGINX errors, and I have to manually, each time, execute the following:

      cat /var/log/nginx/error.log
      sudo rm -rf /etc/nginx/applications/config-that-was-failing-on-errorlog.conf
      sudo systemctl start nginx
      

      Adding/Starting/Installing apps shows the following:

      Task Error
      If a configuration, update, restore or backup action resulted in an error, you can retry the task.
      An error occurred during the start app operation: Nginx Error: Error reloading nginx: reload exited with code 1 signal null
      

      An App was showing Error : Nginx Error - Error reloading nginx: reload exited with code 1 signal null, and when looking at the logs it initially errored, but then it started, so I manually navigated to the page and it work, despite Cloudron always and still showing it as errored, and not being able to access from the Cloudron Homepage. What can I do?

      Here's the error shown in error.log for most apps related to nginx:

      Aug 17 00:34:05 box:settings initCache: pre-load settings
      Aug 17 00:34:05 box:taskworker Starting task 551. Logs are at /home/yellowtent/platformdata/logs/c0593d99-cd86-408d-9f3c-f126a58bb0cb/apptask.log
      Aug 17 00:34:05 box:tasks 551: {"percent":2,"error":null}
      Aug 17 00:34:05 box:apptask taiga.mydomain.org startTask installationState: pending_configure runState: running
      Aug 17 00:34:05 box:tasks 551: {"percent":10,"message":"Cleaning up old install"}
      Aug 17 00:34:05 box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
      Aug 17 00:34:05 box:shell reload (stdout): nginx: [emerg] no host in upstream ":8080" in /etc/nginx/applications/1c65ccf7-5bd1-447f-9566-746fb8ed4efb.conf:136
      Aug 17 00:34:05 box:shell reload code: 1, signal: null
      Aug 17 00:34:05 box:apptask taiga.mydomain.org error reconfiguring: BoxError: Error reloading nginx: reload exited with code 1 signal null
      at /home/yellowtent/box/src/reverseproxy.js:194:36
      at f (/home/yellowtent/box/node_modules/once/once.js:25:25)
      at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:77:9)
      at ChildProcess.emit (events.js:315:20)
      at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12) {
      reason: 'Nginx Error',
      details: {}
      Aug 17 00:34:05 box:taskworker Task took 0.175 seconds
      Aug 17 00:34:05 box:tasks setCompleted - 551: {"result":null,"error":{"stack":"BoxError: Error reloading nginx: reload exited with code 1 signal null\n at /home/yellowtent/box/src/reverseproxy.js:194:36\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:77:9)\n at ChildProcess.emit (events.js:315:20)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)","name":"BoxError","reason":"Nginx Error","details":{},"message":"Error reloading nginx: reload exited with code 1 signal null"}}
      Aug 17 00:34:05 box:tasks 551: {"percent":100,"result":null,"error":{"stack":"BoxError: Error reloading nginx: reload exited with code 1 signal null\n at /home/yellowtent/box/src/reverseproxy.js:194:36\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:77:9)\n at ChildProcess.emit (events.js:315:20)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)","name":"BoxError","reason":"Nginx Error","details":{},"message":"Error reloading nginx: reload exited with code 1 signal null"}}
      

      It's getting quite annoying, and I hope you can help to fix it, as you can read there are multiple problems, thanks in advance.

      girish 1 Reply Last reply Reply Quote 0
      • girish
        girish Staff @revck last edited by

        @revck If you look into journalctl -u nginx , it will usually mention what line of the config is failing. Can you please check?

        R 1 Reply Last reply Reply Quote 0
        • R
          revck @girish last edited by

          @girish definitely, I did check it previously and seems no error is found, here's what I get:

          /etc/nginx/applications$ journalctl -u nginx
          -- Logs begin at Mon 2021-08-16 22:35:16 UTC, end at Wed 2021-08-18 01:44:22 UTC. --
          -- No entries --
          
          nebulon 1 Reply Last reply Reply Quote 0
          • nebulon
            nebulon Staff @revck last edited by

            @revck so from your first post, it looks like you are aware of which config file is failing. Do you see anything suspicious in that one, like some encoding issue or is a special non latin1 domain used for those?

            Further, have you added custom nginx configs which may be included and confusing the system?

            Finally if you want us to take a direct look at your server, please enable remote support send us a mail with your dashboard domain and reference to this thread to support@cloudron.io

            nebulon 1 Reply Last reply Reply Quote 0
            • nebulon
              nebulon Staff @nebulon last edited by

              I am currently debugging that instance, but just for others to read up, using nginx -s reload as root usually reveals the syntax errors in config files right away, like it was in this instance as well.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Powered by NodeBB