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 Migration to new server failed, can't reach dashboard

    Support
    2
    6
    200
    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.
    • ianhyzy
      ianhyzy last edited by

      I moved my cloudron install to a new server and used the restore option. All my appears appeared briefly, but then all showed "error" on the dashboard so I rebooted the box. Now, I can't get to the dashboard at all - it looks like an Nginx issue (?)

      root@my:~# /home/yellowtent/box/setup/start.sh
==> Cloudron Start
media:x:500:
==> 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
Error response from daemon: network with name cloudron already exists
==> Ensuring directories
==> Configuring journald
==> Setting up unbound
==> 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
==> Configuring sudoers
==> Configuring collectd
==> Configuring logrotate
==> Adding motd message for admins
==> Configuring nginx
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for details.

      root@my:~#

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

        Looks like you have hit https://forum.cloudron.io/topic/4267/installation-failed-due-to-nginx-config-error ?

        To get going, please remove the /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf file and then nginx should start again.

        As mentioned in the other post, I will revert that alltube release for a start until fixed. In your case you have to downgrade/restore the app afterwards to an older version.

        ianhyzy 2 Replies Last reply Reply Quote 1
        • nebulon
          nebulon Staff last edited by

          Can you see the nginx logs via journalctl -u nginx and cat /var/log/nginx/error.log
          Also you can start/restart nginx with systemctl start nginx (not that if it is not running at all the systemd unit restart subcommand is not reliable)

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

            @nebulon said in Migration to new server failed, can't reach dashboard:

            cat /var/log/nginx/error.log

            2021/01/25 03:38:34 [notice] 26887#26887: signal process started
2021/01/25 04:28:06 [notice] 27066#27066: signal process started
2021/01/25 04:31:45 [notice] 29714#29714: signal process started
2021/01/25 04:31:45 [notice] 29755#29755: signal process started
2021/01/25 04:31:45 [notice] 29757#29757: signal process started
2021/01/25 04:32:14 [notice] 29831#29831: signal process started
2021/01/25 04:34:51 [notice] 30961#30961: signal process started
2021/01/25 04:34:51 [emerg] 26645#26645: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:51 [notice] 30964#30964: signal process started
2021/01/25 04:34:51 [emerg] 26645#26645: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:51 [emerg] 30969#30969: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:52 [emerg] 31090#31090: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:52 [emerg] 31093#31093: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:52 [emerg] 31097#31097: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:53 [emerg] 31169#31169: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:53 [emerg] 31187#31187: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:53 [emerg] 31188#31188: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:54 [emerg] 31393#31393: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:54 [emerg] 31411#31411: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:54 [emerg] 31420#31420: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:54 [emerg] 31489#31489: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:54 [emerg] 31517#31517: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:54 [emerg] 31516#31516: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:55 [emerg] 31570#31570: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:34:55 [emerg] 31592#31592: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:36:22 [emerg] 31837#31837: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:36:39 [emerg] 31892#31892: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:36:45 [emerg] 31936#31936: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:37:07 [emerg] 31989#31989: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:41:28 [emerg] 933#933: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:41:28 [emerg] 959#959: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:41:28 [emerg] 966#966: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:41:28 [emerg] 988#988: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:41:29 [emerg] 999#999: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:41:33 [emerg] 3266#3266: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 04:42:03 [emerg] 3942#3942: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 15:15:35 [emerg] 4957#4957: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 15:15:35 [emerg] 4970#4970: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 15:15:35 [emerg] 4975#4975: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 15:15:35 [emerg] 4977#4977: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
2021/01/25 15:15:35 [emerg] 4979#4979: location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163

            For sysctl here's a snippet:

            Jan 25 04:41:28 my.socialism.tools systemd[1]: Starting nginx - high performance web server...
Jan 25 04:41:28 my.socialism.tools nginx[933]: nginx: [emerg] location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
Jan 25 04:41:28 my.socialism.tools systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Jan 25 04:41:28 my.socialism.tools systemd[1]: nginx.service: Failed with result 'exit-code'.
Jan 25 04:41:28 my.socialism.tools systemd[1]: Failed to start nginx - high performance web server.
Jan 25 04:41:28 my.socialism.tools systemd[1]: nginx.service: Scheduled restart job, restart counter is at 1.
Jan 25 04:41:28 my.socialism.tools systemd[1]: Stopped nginx - high performance web server.
Jan 25 04:41:28 my.socialism.tools systemd[1]: Starting nginx - high performance web server...
Jan 25 04:41:28 my.socialism.tools nginx[959]: nginx: [emerg] location "!/extractors" is outside location "/" in /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf:163
Jan 25 04:41:28 my.socialism.tools systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Jan 25 04:41:28 my.socialism.tools systemd[1]: nginx.service: Failed with result 'exit-code'.
Jan 25 04:41:28 my.socialism.tools systemd[1]: Failed to start nginx - high performance web server.
            1 Reply Last reply Reply Quote 0
            • nebulon
              nebulon Staff last edited by

              Looks like you have hit https://forum.cloudron.io/topic/4267/installation-failed-due-to-nginx-config-error ?

              To get going, please remove the /etc/nginx/applications/1368c982-f55e-425c-9209-4d9c3009a0aa.conf file and then nginx should start again.

              As mentioned in the other post, I will revert that alltube release for a start until fixed. In your case you have to downgrade/restore the app afterwards to an older version.

              ianhyzy 2 Replies Last reply Reply Quote 1
              • ianhyzy
                ianhyzy @nebulon last edited by

                @nebulon that fixed it, thank you for the quick response!

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

                  @nebulon one more issue that's popping up - the server completely stops working after a few minutes of everything working fine and I can't SSH in either. Any way to find out what's doing that?

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