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
  • Brite
  • 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 - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Web Gui isn't loading

Web Gui isn't loading

Scheduled Pinned Locked Moved Unsolved Support
3 Posts 2 Posters 10 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.
  • H Online
    H Online
    hayoken2000
    wrote last edited by james
    #1

    Description

    I had a power outage, and when I came back, my GUI was running, but multiple services were down. I rebooted the server again, and then my GUI isn't loading. I have been band-aiding this server for a while, and I am at the point where I just want to do a fresh install of Ubuntu and redownload Cloudron. I do have a current backup on a local nfs server on the network. However, I did create two partitions on the Cloudron server: one running the main server, and a second partition on a different raid for installing the apps. Do I need to keep the same raid and partition setup for restoring my backups, or will the restore work with any partition setup I create afterward? I haven't done a restore for the whole server before, so how would I go about it after installing a fresh copy of Cloudron, attaching my local nfs server with the backups on, and restoring it?

    Troubleshooting

    Vendor: Dell Inc. Product: PowerEdge R720
    Linux: 6.8.0-106-generic
    Ubuntu: jammy 22.04
    Processor: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz x 32
    RAM: 197984212KB
    Disk: /dev/sda2       2.8T
    [OK]    node version is correct
    [OK]    IPv6 is enabled in kernel. No public IPv6 address
    [OK]    docker is running
    [OK]    docker version is correct
    [OK]    MySQL is running
    [OK]    nginx is running
    [OK]    dashboard cert is valid
    [OK]    dashboard is reachable via loopback
    [OK]    box v8.3.1 is running
    [OK]    netplan is good
    [OK]    DNS is resolving via systemd-resolved
    [OK]    Dashboard is reachable via domain name
    [OK]    Domain nookscape.com is valid and has not expired
    [OK]    unbound is running
    
    

    Box Log

    nookscape@Cloudron:~$ tail -n 80 /home/yellowtent/platformdata/logs/box.log
    2026-03-27T14:05:42.019Z box:shell All tasks stopped
    
    2026-03-27T14:05:46.195Z box:server ==========================================
    2026-03-27T14:05:46.197Z box:server            Cloudron 8.3.1
    2026-03-27T14:05:46.197Z box:server ==========================================
    2026-03-27T14:05:46.197Z box:platform initialize: start platform
    2026-03-27T14:05:46.241Z box:tasks stopAllTasks: stopping all tasks
    2026-03-27T14:05:46.241Z box:shell tasks /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
    2026-03-27T14:05:46.290Z box:shell All tasks stopped
    
    2026-03-27T14:05:46.313Z box:locks releaseAll: all locks released
    2026-03-27T14:05:46.319Z box:reverseproxy writeDashboardConfig: writing dashboard config for nookscape.com
    2026-03-27T14:05:46.329Z box:shell reverseproxy: openssl x509 -in /home/yellowtent/platformdata/nginx/cert/_.nookscape.com.cert -noout -ocsp_uri
    2026-03-27T14:05:46.345Z box:shell reverseproxy /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
    2026-03-27T14:05:46.866Z box:platform onActivated: starting post activation services
    2026-03-27T14:05:46.867Z box:platform startInfra: checking infrastructure
    2026-03-27T14:05:46.867Z box:platform startInfra: updating infrastructure from 48.0.0 to 49.8.0
    2026-03-27T14:05:46.868Z box:platform markApps: reconfiguring apps
    2026-03-27T14:05:46.868Z box:reverseproxy removeAppConfigs: removing app nginx configs
    2026-03-27T14:05:46.925Z box:platform removeAllContainers: removing all containers for infra upgrade
    2026-03-27T14:05:46.925Z box:shell platform: docker ps -qa --filter label=isCloudronManaged
    2026-03-27T14:05:46.956Z box:platform removeAllContainers: stopping and removing 11ed734458cd
    2026-03-27T14:05:46.956Z box:shell platform: docker stop 11ed734458cd
    2026-03-27T14:05:50.049Z box:shell platform: docker rm -f 11ed734458cd
    2026-03-27T14:05:50.150Z box:platform removeAllContainers: stopping and removing 5292fc94027c
    2026-03-27T14:05:50.150Z box:shell platform: docker stop 5292fc94027c
    2026-03-27T14:06:00.286Z box:shell platform: docker rm -f 5292fc94027c
    2026-03-27T14:06:00.324Z box:platform removeAllContainers: stopping and removing d3c9dbea3399
    2026-03-27T14:06:00.324Z box:shell platform: docker stop d3c9dbea3399
    2026-03-27T14:06:04.555Z box:shell platform: docker rm -f d3c9dbea3399
    2026-03-27T14:06:04.592Z box:platform createDockerNetwork: recreating docker network
    2026-03-27T14:06:04.592Z box:shell platform: docker network rm -f cloudron
    2026-03-27T14:06:04.974Z box:shell platform: docker network create --subnet=172.18.0.0/16 --ip-range=172.18.0.0/20 --gateway=172.18.0.1 --ipv6 --subnet=fd00:c107:d509::/64 cloudron
    2026-03-27T14:06:05.210Z box:services startServices: 48.0.0 -> 49.8.0. starting all services
    2026-03-27T14:06:05.210Z box:mailserver startMail: starting
    2026-03-27T14:06:05.220Z box:mailserver restart: restarting mail container with mailFqdn:my.nookscape.com mailDomain:nookscape.com
    2026-03-27T14:06:05.227Z box:locks write: current locks: {"mail_restart":null}
    2026-03-27T14:06:05.227Z box:locks acquire: mail_restart
    2026-03-27T14:06:05.244Z box:mailserver configureMail: stopping and deleting previous mail container
    2026-03-27T14:06:05.288Z box:mailserver createMailConfig: generating mail config with my.nookscape.com
    2026-03-27T14:06:05.306Z box:mailserver configureMail: starting mail container
    2026-03-27T14:06:05.306Z box:shell mailserver: /bin/bash -c docker run --restart=always -d --name=mail                 --net cloudron                 --net-alias mail                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=mail                 -m 8589934592                 --memory-swap -1                 --dns 172.18.0.1                 --dns-search=.                 --ip 172.18.30.4                 -e CLOUDRON_MAIL_TOKEN=4b4fc1caf5b3ebd7d1d8d3630d1e659c2b5adf72c24eb40d8ab58de2fdc94e7dfb190fdc95335e2d868c1040b3fa29b586b6e14994d2d07934cd016d2d4f71a150052d8f4ff182244424531da13b7730071d8204ba3c59a23e300a82722d91db0b6a782856e719f3d1c0ba62f36bfe79fe6ebfbe4ed7b1a7c33a4ef44db0cd5c                 -e CLOUDRON_RELAY_TOKEN=d75d0a5062cb85cae5a22b96996cc487fbe4f4ffa59aee7e53ea765f210c13f479805e415f1cc6dc86ed04024795ae2e03708acea19e6efe2c273a5ef28a6f1e5e0fb6fb7362a17b812e6eaba378c3fa2b745db06f5ff16c603fb87c6dcc0fc5fa714d3470750d1c7f0fbf5706005adfe7846707a68c3348adbab45b2d4cb9f1                 -e LOGLEVEL=info                 -v /home/yellowtent/boxdata/mail:/app/data                 -v /home/yellowtent/platformdata/addons/mail:/etc/mail:ro                 -p 587:2587 -p 993:9993 -p 4190:4190 -p 25:2587 -p 465:2465 -p 995:9995                 --label isCloudronManaged=true                 --read-only -v /run -v /tmp registry.docker.com/cloudron/mail:3.15.0@sha256:c93b5a83fc4e775bda4e05010bd19e5a658936e7a09cf7e51281e3696fde4536
    2026-03-27T14:06:06.969Z box:locks write: current locks: {}
    2026-03-27T14:06:06.969Z box:locks release: mail_restart
    2026-03-27T14:06:06.974Z box:services startTurn: stopping and deleting previous turn container
    2026-03-27T14:06:06.980Z box:services startTurn: starting turn container
    2026-03-27T14:06:06.980Z box:shell services: /bin/bash -c docker run --restart=always -d --name=turn                 --hostname turn                 --net host                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=turn                 -m 5234491392                 --memory-swap -1                 -e CLOUDRON_TURN_SECRET=ab487e39af5147f386b83a974db0b51                 -e CLOUDRON_REALM=my.nookscape.com                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/turn:1.8.0@sha256:cdbe83c3c83b8f25de3a5814b121eb941b457dca7127d2e6ff446c7a0cfa1570
    2026-03-27T14:06:07.203Z box:services startMysql: stopping and deleting previous mysql container
    2026-03-27T14:06:07.208Z box:services startMysql: starting mysql container
    2026-03-27T14:06:07.208Z box:shell services: /bin/bash -c docker run --restart=always -d --name=mysql                 --hostname mysql                 --net cloudron                 --net-alias mysql                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=mysql                 --ip 172.18.30.1                 -e CLOUDRON_MYSQL_TOKEN=2a0c32df4cd0a0195db9b97a73f0d84a30fd085351cd155691471b15689d896d8ab08aaf383475f0235de71379cb39ca7a2196572f75e5e43277d5b67213b7f70dabc8936c62113160c7cf832c6f41912788e3dac3cdddc93cb077ada27ed82ec81991f902b3d11f1c0696a0ddda312bba1b4b93f3f7e02761a4f8dbcff2e715                 -e CLOUDRON_MYSQL_ROOT_HOST=172.18.0.1                 -e CLOUDRON_MYSQL_ROOT_PASSWORD=420f78f4299c8c941cebd91e9f010192800c8b2d444dcad379fdb67cdd5377adb78e49bbe6b4d9d32c5897219e9b1b6360ee234db0faa47c404c5df309f51ca3483d7ff5fa5792381ef8a8391e1881d3e3893695ffee36fcef9cb18d65c0eb30764963a490efb94c7e225fcfc2b6c173180026f4315595900e2cf64c8d6f55d9                 -v /home/yellowtent/platformdata/mysql:/var/lib/mysql                 --label isCloudronManaged=true                 --cap-add SYS_NICE                 --read-only -v /tmp -v /run registry.docker.com/cloudron/mysql:3.5.0@sha256:969ea5b2f91861940ca6309c7676c52e479d2a864ba3aabd08a4266799707280
    2026-03-27T14:06:07.844Z box:services Waiting for mysql
    2026-03-27T14:06:10.914Z box:services Attempt 1 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:06:29.025Z box:services Attempt 2 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:06:47.137Z box:services Attempt 3 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:07:05.249Z box:services Attempt 4 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:07:23.361Z box:services Attempt 5 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:07:41.473Z box:services Attempt 6 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:07:59.585Z box:services Attempt 7 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:08:17.697Z box:services Attempt 8 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:08:35.809Z box:services Attempt 9 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:08:53.921Z box:services Attempt 10 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:09:12.034Z box:services Attempt 11 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:09:30.146Z box:services Attempt 12 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:09:48.257Z box:services Attempt 13 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:10:06.369Z box:services Attempt 14 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:10:24.481Z box:services Attempt 15 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:10:42.593Z box:services Attempt 16 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:11:00.705Z box:services Attempt 17 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:11:18.817Z box:services Attempt 18 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:11:36.929Z box:services Attempt 19 failed. Will retry: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:11:55.042Z box:platform startInfra: Failed to start services. retry=false (attempt 0): Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
    2026-03-27T14:11:55.043Z box:platform BoxError: Network error waiting for mysql: connect EHOSTUNREACH 172.18.30.1:3000
        at /home/yellowtent/box/src/services.js:603:33
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
        at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20)
        at async waitForContainer (/home/yellowtent/box/src/services.js:598:5)
        at async startMysql (/home/yellowtent/box/src/services.js:1251:9)
        at async Object.startServices (/home/yellowtent/box/src/services.js:825:9)
        at async startInfra (/home/yellowtent/box/src/platform.js:147:13)
        at async onActivated (/home/yellowtent/box/src/platform.js:207:5)
    nookscape@Cloudron:~$
    
    1 Reply Last reply
    0
    • jamesJ Offline
      jamesJ Offline
      james
      Staff
      wrote last edited by
      #2

      Hello @hayoken2000
      You are still on Cloudron version 8.3.1, you should update your cloudron if possible.
      From the log I can see that the mysql docker container is not starting correctly.
      Please check the mysql docker logs with:

      docker logs mysql
      
      1 Reply Last reply
      0
      • H Online
        H Online
        hayoken2000
        wrote last edited by hayoken2000
        #3

        @james I can't update; I don't have a web GUI.

        Here are the logs:

        nookscape@Cloudron:~$ docker logs mysql
        Detected existing installation
        chown: warning: '.' should be ':': 'mysql.mysql'
        Resetting root password to 420f78f4299c8c941cebd91e9f010192800c8b2d444dcad379fdb67cdd5377adb78e49bbe6b4d9d32c5897219e9b1b6360ee234db0faa47c404c5df309f51ca3483d7ff5fa5792381ef8a8391e1881d3e3893695ffee36fcef9cb18d65c0eb30764963a490efb94c7e225fcfc2b6c173180026f4315595900e2cf64c8d6f55d9
        Waiting with password
        Waiting for MySQL to come up
        Waiting for MySQL to come up
        Waiting for MySQL to come up
        Waiting for MySQL to come up
        Waiting for MySQL to come up
        Waiting for MySQL to come up
        mysqladmin: [Warning] Using a password on the command line interface can be insecure.
        Starting supervisor
        2026-03-27 14:06:16,202 INFO Included extra file "/etc/supervisor/conf.d/mysql-service.conf" during parsing
        2026-03-27 14:06:16,202 INFO Included extra file "/etc/supervisor/conf.d/mysql.conf" during parsing
        2026-03-27 14:06:16,202 INFO Set uid to user 0 succeeded
        2026-03-27 14:06:16,208 INFO RPC interface 'supervisor' initialized
        2026-03-27 14:06:16,208 CRIT Server 'inet_http_server' running without any HTTP authentication checking
        2026-03-27 14:06:16,209 INFO supervisord started with pid 1
        2026-03-27 14:06:17,211 INFO spawned: 'mysql' with pid 74
        2026-03-27 14:06:17,213 INFO spawned: 'mysql-service' with pid 75
        MySQL service endpoint listening on http://:::3000
        2026-03-27 14:06:18,469 INFO success: mysql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
        2026-03-27 14:06:18,469 INFO success: mysql-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
        nookscape@Cloudron:~$

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        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