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 and applications unreachable after recovery from full disk

Dashboard and applications unreachable after recovery from full disk

Scheduled Pinned Locked Moved Solved Support
19 Posts 5 Posters 4.1k Views 5 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.
  • robiR Offline
    robiR Offline
    robi
    wrote on last edited by
    #10

    Then please gather the restart portion of nginx, and box logs so we can see what the actual failure is.

    Is box regenerating the nginx configs after restart?
    If so, post the config file that is causing the failure to start.

    Alternatively you can email support@ for additional assistance.

    Conscious tech

    BrutalBirdieB whitespaceW 2 Replies Last reply
    0
    • robiR robi

      Then please gather the restart portion of nginx, and box logs so we can see what the actual failure is.

      Is box regenerating the nginx configs after restart?
      If so, post the config file that is causing the failure to start.

      Alternatively you can email support@ for additional assistance.

      BrutalBirdieB Offline
      BrutalBirdieB Offline
      BrutalBirdie
      Partner
      wrote on last edited by
      #11

      @whitespace I had a similar issue yesterday, please post the needed logs so we can see the real error message for further assistance.

      Or like @robi suggested write an E-Mail to support@cloudron.io

      Like my work? Consider donating a drink. Cheers!

      1 Reply Last reply
      0
      • robiR robi

        Then please gather the restart portion of nginx, and box logs so we can see what the actual failure is.

        Is box regenerating the nginx configs after restart?
        If so, post the config file that is causing the failure to start.

        Alternatively you can email support@ for additional assistance.

        whitespaceW Offline
        whitespaceW Offline
        whitespace
        wrote on last edited by
        #12

        @robi

        Output of

        systectl status nginx.service
        

        is

        ● nginx.service - nginx - high performance web server
             Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
            Drop-In: /etc/systemd/system/nginx.service.d
                     └─cloudron.conf
             Active: failed (Result: exit-code) since Fri 2022-08-19 10:18:19 UTC; 6s ago
               Docs: http://nginx.org/en/docs/
            Process: 5047 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE)
        
        Aug 19 10:18:19 1001364-346 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
        Aug 19 10:18:19 1001364-346 systemd[1]: Stopped nginx - high performance web server.
        Aug 19 10:18:19 1001364-346 systemd[1]: nginx.service: Start request repeated too quickly.
        Aug 19 10:18:19 1001364-346 systemd[1]: nginx.service: Failed with result 'exit-code'.
        Aug 19 10:18:19 1001364-346 systemd[1]: Failed to start nginx - high performance web server.
        

        Is box regenerating the nginx configs after restart?

        It seems so. They appear inside the folder and have the expected default values.


        box.log output after

        systemctl box restart
        

        is

        2022-08-19T10:26:05.740Z box:server ==========================================
        2022-08-19T10:26:05.748Z box:server            Cloudron 7.2.5  
        2022-08-19T10:26:05.748Z box:server ==========================================
        2022-08-19T10:26:05.794Z box:settings initCache: pre-load settings
        2022-08-19T10:26:05.808Z box:tasks stopAllTasks: stopping all tasks
        2022-08-19T10:26:05.808Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
        2022-08-19T10:26:05.820Z box:shell stopTask (stdout): sudo: unable to resolve host 1001364-346: Name or service not known
        
        Cloudron is up and running. Logs are at /home/yellowtent/platformdata/logs/box.log
        2022-08-19T10:26:05.864Z box:shell removeCollectdProfile spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/configurecollectd.sh remove cloudron-backup
        2022-08-19T10:26:05.871Z box:shell removeCollectdProfile (stdout): sudo: unable to resolve host 1001364-346: Name or service not known
        
        2022-08-19T10:26:05.875Z box:shell removeCollectdProfile (stdout): Restarting collectd
        
        2022-08-19T10:26:05.939Z box:shell removeCollectdProfile (stdout): Removing collectd stats of cloudron-backup
        
        2022-08-19T10:26:05.946Z box:reverseproxy writeDashboardConfig: writing admin config for myserver.com
        Can't open /home/yellowtent/platformdata/nginx/cert/myserver.com.host.cert for reading, No such file or directory
        139761371608384:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('/home/yellowtent/platformdata/nginx/cert/myserver.com.host.cert','r')
        139761371608384:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:76:
        unable to load certificate
        2022-08-19T10:26:05.969Z box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
        2022-08-19T10:26:05.978Z box:shell reload (stdout): sudo: unable to resolve host 1001364-346: Name or service not known
        
        2022-08-19T10:26:05.996Z box:shell reload (stdout): nginx: [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/myserver.com.host.cert": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/home/yellowtent/platformdata/nginx/cert/myserver.com.host.cert','r') error:2006D080:BIO routines:BIO_new_file:no such file)
        
        2022-08-19T10:26:05.996Z box:shell reload code: 1, signal: null
        2022-08-19T10:26:05.997Z box:cloudron Startup task at index 2 failed: Error reloading nginx: reload exited with code 1 signal null
        2022-08-19T10:26:06.014Z box:cloudron onActivated: running post activation tasks
        2022-08-19T10:26:06.014Z box:platform initializing addon infrastructure
        2022-08-19T10:26:06.015Z box:platform platform is uptodate at version 49.0.0
        2022-08-19T10:26:06.015Z box:platform onPlatformReady: platform is ready. infra changed: false
        2022-08-19T10:26:06.015Z box:apps schedulePendingTasks: scheduling app tasks
        2022-08-19T10:26:06.024Z box:cron startJobs: starting cron jobs
        2022-08-19T10:26:06.035Z box:cron backupConfigChanged: schedule 00 00 3,23 * * 0 (Europe/Berlin)
        2022-08-19T10:26:06.038Z box:cron autoupdatePatternChanged: pattern - 00 00 1,3,5,23 * * 1,3,4,6 (Europe/Berlin)
        2022-08-19T10:26:06.040Z box:cron Dynamic DNS setting changed to false
        2022-08-19T10:26:06.041Z box:dockerproxy startDockerProxy: started proxy on port 3003
        2022-08-19T10:26:10.217Z box:apphealthmonitor app health: 7 alive / 1 dead.
        2022-08-19T10:26:20.155Z box:apphealthmonitor app health: 7 alive / 1 dead.
        2022-08-19T10:26:30.190Z box:apphealthmonitor app health: 7 alive / 1 dead.
        
        
        robiR 1 Reply Last reply
        0
        • whitespaceW whitespace

          @robi

          Output of

          systectl status nginx.service
          

          is

          ● nginx.service - nginx - high performance web server
               Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
              Drop-In: /etc/systemd/system/nginx.service.d
                       └─cloudron.conf
               Active: failed (Result: exit-code) since Fri 2022-08-19 10:18:19 UTC; 6s ago
                 Docs: http://nginx.org/en/docs/
              Process: 5047 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE)
          
          Aug 19 10:18:19 1001364-346 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
          Aug 19 10:18:19 1001364-346 systemd[1]: Stopped nginx - high performance web server.
          Aug 19 10:18:19 1001364-346 systemd[1]: nginx.service: Start request repeated too quickly.
          Aug 19 10:18:19 1001364-346 systemd[1]: nginx.service: Failed with result 'exit-code'.
          Aug 19 10:18:19 1001364-346 systemd[1]: Failed to start nginx - high performance web server.
          

          Is box regenerating the nginx configs after restart?

          It seems so. They appear inside the folder and have the expected default values.


          box.log output after

          systemctl box restart
          

          is

          2022-08-19T10:26:05.740Z box:server ==========================================
          2022-08-19T10:26:05.748Z box:server            Cloudron 7.2.5  
          2022-08-19T10:26:05.748Z box:server ==========================================
          2022-08-19T10:26:05.794Z box:settings initCache: pre-load settings
          2022-08-19T10:26:05.808Z box:tasks stopAllTasks: stopping all tasks
          2022-08-19T10:26:05.808Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
          2022-08-19T10:26:05.820Z box:shell stopTask (stdout): sudo: unable to resolve host 1001364-346: Name or service not known
          
          Cloudron is up and running. Logs are at /home/yellowtent/platformdata/logs/box.log
          2022-08-19T10:26:05.864Z box:shell removeCollectdProfile spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/configurecollectd.sh remove cloudron-backup
          2022-08-19T10:26:05.871Z box:shell removeCollectdProfile (stdout): sudo: unable to resolve host 1001364-346: Name or service not known
          
          2022-08-19T10:26:05.875Z box:shell removeCollectdProfile (stdout): Restarting collectd
          
          2022-08-19T10:26:05.939Z box:shell removeCollectdProfile (stdout): Removing collectd stats of cloudron-backup
          
          2022-08-19T10:26:05.946Z box:reverseproxy writeDashboardConfig: writing admin config for myserver.com
          Can't open /home/yellowtent/platformdata/nginx/cert/myserver.com.host.cert for reading, No such file or directory
          139761371608384:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('/home/yellowtent/platformdata/nginx/cert/myserver.com.host.cert','r')
          139761371608384:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:76:
          unable to load certificate
          2022-08-19T10:26:05.969Z box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
          2022-08-19T10:26:05.978Z box:shell reload (stdout): sudo: unable to resolve host 1001364-346: Name or service not known
          
          2022-08-19T10:26:05.996Z box:shell reload (stdout): nginx: [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/myserver.com.host.cert": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/home/yellowtent/platformdata/nginx/cert/myserver.com.host.cert','r') error:2006D080:BIO routines:BIO_new_file:no such file)
          
          2022-08-19T10:26:05.996Z box:shell reload code: 1, signal: null
          2022-08-19T10:26:05.997Z box:cloudron Startup task at index 2 failed: Error reloading nginx: reload exited with code 1 signal null
          2022-08-19T10:26:06.014Z box:cloudron onActivated: running post activation tasks
          2022-08-19T10:26:06.014Z box:platform initializing addon infrastructure
          2022-08-19T10:26:06.015Z box:platform platform is uptodate at version 49.0.0
          2022-08-19T10:26:06.015Z box:platform onPlatformReady: platform is ready. infra changed: false
          2022-08-19T10:26:06.015Z box:apps schedulePendingTasks: scheduling app tasks
          2022-08-19T10:26:06.024Z box:cron startJobs: starting cron jobs
          2022-08-19T10:26:06.035Z box:cron backupConfigChanged: schedule 00 00 3,23 * * 0 (Europe/Berlin)
          2022-08-19T10:26:06.038Z box:cron autoupdatePatternChanged: pattern - 00 00 1,3,5,23 * * 1,3,4,6 (Europe/Berlin)
          2022-08-19T10:26:06.040Z box:cron Dynamic DNS setting changed to false
          2022-08-19T10:26:06.041Z box:dockerproxy startDockerProxy: started proxy on port 3003
          2022-08-19T10:26:10.217Z box:apphealthmonitor app health: 7 alive / 1 dead.
          2022-08-19T10:26:20.155Z box:apphealthmonitor app health: 7 alive / 1 dead.
          2022-08-19T10:26:30.190Z box:apphealthmonitor app health: 7 alive / 1 dead.
          
          
          robiR Offline
          robiR Offline
          robi
          wrote on last edited by
          #13

          @whitespace that is not an nginx log. See how it says systemd[1]?

          Conscious tech

          whitespaceW BrutalBirdieB 2 Replies Last reply
          0
          • robiR robi

            @whitespace that is not an nginx log. See how it says systemd[1]?

            whitespaceW Offline
            whitespaceW Offline
            whitespace
            wrote on last edited by whitespace
            #14
            journalctl -u nginx -fa
            

            gives me

            Aug 19 10:50:42 1001364-346 systemd[1]: Starting nginx - high performance web server...
            Aug 19 10:50:42 1001364-346 nginx[11878]: nginx: [emerg] cannot load certificate key "/home/yellowtent/platformdata/nginx/cert/_.myserver.com.key": PEM_read_bio_PrivateKey() failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: ANY PRIVATE KEY)
            Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
            Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Failed with result 'exit-code'.
            Aug 19 10:50:42 1001364-346 systemd[1]: Failed to start nginx - high performance web server.
            Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
            Aug 19 10:50:42 1001364-346 systemd[1]: Stopped nginx - high performance web server.
            Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Start request repeated too quickly.
            Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Failed with result 'exit-code'.
            Aug 19 10:50:42 1001364-346 systemd[1]: Failed to start nginx - high performance web server.
              
            
            robiR 1 Reply Last reply
            0
            • robiR robi

              @whitespace that is not an nginx log. See how it says systemd[1]?

              BrutalBirdieB Offline
              BrutalBirdieB Offline
              BrutalBirdie
              Partner
              wrote on last edited by BrutalBirdie
              #15

              @robi said in Dashboard and applications unreachable after recovery from full disk:

              @whitespace that is not an nginx log. See how it says systemd[1]?

              But it includes the nginx errors 🙂

              2022-08-19T10:26:05.996Z box:shell reload (stdout): nginx: [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/myserver.com.host.cert": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/home/yellowtent/platformdata/nginx/cert/myserver.com.host.cert','r') error:2006D080:BIO routines:BIO_new_file:no such file)
              

              Nginx has missing certificates. @nebulon fixe this yesterday for one of my instances.
              It might be best to send a message to the support.

              Like my work? Consider donating a drink. Cheers!

              1 Reply Last reply
              1
              • whitespaceW whitespace
                journalctl -u nginx -fa
                

                gives me

                Aug 19 10:50:42 1001364-346 systemd[1]: Starting nginx - high performance web server...
                Aug 19 10:50:42 1001364-346 nginx[11878]: nginx: [emerg] cannot load certificate key "/home/yellowtent/platformdata/nginx/cert/_.myserver.com.key": PEM_read_bio_PrivateKey() failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: ANY PRIVATE KEY)
                Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
                Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Failed with result 'exit-code'.
                Aug 19 10:50:42 1001364-346 systemd[1]: Failed to start nginx - high performance web server.
                Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
                Aug 19 10:50:42 1001364-346 systemd[1]: Stopped nginx - high performance web server.
                Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Start request repeated too quickly.
                Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Failed with result 'exit-code'.
                Aug 19 10:50:42 1001364-346 systemd[1]: Failed to start nginx - high performance web server.
                  
                
                robiR Offline
                robiR Offline
                robi
                wrote on last edited by
                #16

                @whitespace from another message in the log, it doesn't appear that the system knows it's own hostname.

                Please make sure to set one so it sticks after reboot.

                @BrutalBirdie yes, I missed that from the long scroll to the right. 🙏

                Conscious tech

                1 Reply Last reply
                0
                • girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #17

                  @whitespace I replied to you from support@. We have to delete the nginx config file and also the bad key/cert and then "systemctl restart box". This will re-generate the config file and the certs.

                  In next release, this is done automatically. We check if the key/cert are bad files and re-sync things to disk automatically.

                  whitespaceW 1 Reply Last reply
                  2
                  • girishG Offline
                    girishG Offline
                    girish
                    Staff
                    wrote on last edited by
                    #18

                    Resolved in support@

                    1 Reply Last reply
                    2
                    • girishG girish marked this topic as a question on
                    • girishG girish has marked this topic as solved on
                    • girishG girish

                      @whitespace I replied to you from support@. We have to delete the nginx config file and also the bad key/cert and then "systemctl restart box". This will re-generate the config file and the certs.

                      In next release, this is done automatically. We check if the key/cert are bad files and re-sync things to disk automatically.

                      whitespaceW Offline
                      whitespaceW Offline
                      whitespace
                      wrote on last edited by
                      #19

                      Thank you very much for resolving the issue. I would love to understand what i did wrong.

                      I tried deleting the nginx.conf and certs and let them be regenerated as you have described in other threads. Yet I did not manage to get nginx back up and running. Are there additional steps besides deleting cofings, restarting box, nginx and unbound?

                      Muchas Gracias for saving the day!

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