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. Dashboard unavailable

Dashboard unavailable

Scheduled Pinned Locked Moved Solved Support
dashboardunresponsive
7 Posts 2 Posters 1.4k 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.
    • A Offline
      A Offline
      atokelove
      wrote on last edited by girish
      #1

      Hello!

      I've been running this Cloudron server for around 3 years but it became unavailable a couple of days ago. What I've checked so far:

      1. I can ping my.domain.com, and apps like git.domain.com

      2. I can SSH to the server

      3. I've ran /home/yellowtent/box/setup/start.sh which runs with no errors.

      4. systemctl status box is online, systemctl status nginx and systemctl status mysql show as online

      5. docker ps shows my containers running

      6. Latest entries in the cloudron log are as follows:

      2021-02-01T20:40:20.177Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:40:30.171Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:40:40.170Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:40:50.175Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:41:00.224Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:41:10.199Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:41:20.183Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:41:30.180Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:41:40.179Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:41:50.181Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:42:00.189Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:42:10.174Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:42:20.193Z box:apphealthmonitor app health: 7 alive / 0 dead.
      2021-02-01T20:42:30.216Z box:apphealthmonitor app health: 7 alive / 0 dead.
      

      Any help would be greatly appreciated.

      1 Reply Last reply
      0
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #2

        Hi,

        what exactly became unavailable? Are you saying the dashboard cannot be viewed with the browser? Is there a certificate issue or does it just timeout?

        1 Reply Last reply
        0
        • A Offline
          A Offline
          atokelove
          wrote on last edited by
          #3

          Apologies - my.$domain.com does not load in a browser. It times out.

          nebulonN 1 Reply Last reply
          0
          • A atokelove

            Apologies - my.$domain.com does not load in a browser. It times out.

            nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #4

            @atokelove ok, and the IP also resolves correctly to the expected value?

            Can you check if you see a 401 message in the box.logs if you put https://my.domain.com/api/v1/profile in the browser?

            Also check if restarting nginx helps via systemctl restart nginx

            A 1 Reply Last reply
            0
            • nebulonN nebulon

              @atokelove ok, and the IP also resolves correctly to the expected value?

              Can you check if you see a 401 message in the box.logs if you put https://my.domain.com/api/v1/profile in the browser?

              Also check if restarting nginx helps via systemctl restart nginx

              A Offline
              A Offline
              atokelove
              wrote on last edited by
              #5

              @nebulon

              Correct, the hostname resolves to the correct IP

              https://my.domain.com/api/v1/profile also times out - There is no 401 response in /home/yellowtent/platformdata/logs/box.log

              Restarting nginx does not resolve the issue.

              nebulonN 1 Reply Last reply
              0
              • A atokelove

                @nebulon

                Correct, the hostname resolves to the correct IP

                https://my.domain.com/api/v1/profile also times out - There is no 401 response in /home/yellowtent/platformdata/logs/box.log

                Restarting nginx does not resolve the issue.

                nebulonN Offline
                nebulonN Offline
                nebulon
                Staff
                wrote on last edited by nebulon
                #6

                @atokelove maybe you could send a mail to support@cloudron.io and let us know which domain you are using, if you don't want to disclose it here. Maybe we can then spot the issue from outside.

                Ah apparently you already did 🙂

                A 1 Reply Last reply
                1
                • nebulonN nebulon

                  @atokelove maybe you could send a mail to support@cloudron.io and let us know which domain you are using, if you don't want to disclose it here. Maybe we can then spot the issue from outside.

                  Ah apparently you already did 🙂

                  A Offline
                  A Offline
                  atokelove
                  wrote on last edited by
                  #7

                  Update: It is due to the VPS provider blocking ports 80, 443.

                  1 Reply Last reply
                  1
                  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