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. out of space - normal process not working.

out of space - normal process not working.

Scheduled Pinned Locked Moved Solved Support
certificatesdisk space
13 Posts 3 Posters 1.3k Views 3 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.
  • R roofboard

    @subven said in out of space - normal process not working.:

    systemctl restart nginx
    Hi, Thanks for the reply.

    I just did that, I deleted all files in /etc/nginx/cert/, and /etc/nginx/applications/

    Then systemctl restart nginx

    And box is running.... everything is running, but cloudron is still down.

    when i reboot the server

    nginx down and I am back at square 1.

    subvenS Offline
    subvenS Offline
    subven
    wrote on last edited by subven
    #4

    @roofboard said in out of space - normal process not working.:

    I just did that, I deleted all files in /etc/nginx/cert/, and /etc/nginx/applications/

    nginx stuff for Cloudron is at /home/yellowtent/platformdata/nginx/applications 😉 Please post your log output from the journalctl command above. Also please restart box with the given command, not nginx.

    R 1 Reply Last reply
    0
    • subvenS subven

      @roofboard said in out of space - normal process not working.:

      I just did that, I deleted all files in /etc/nginx/cert/, and /etc/nginx/applications/

      nginx stuff for Cloudron is at /home/yellowtent/platformdata/nginx/applications 😉 Please post your log output from the journalctl command above. Also please restart box with the given command, not nginx.

      R Offline
      R Offline
      roofboard
      wrote on last edited by
      #5

      @subven
      Thanks for the reply. Folowing the instructions.
      Here are my commands

      root@my:~# cd /home/yellowtent/platformdata/nginx/applications
      root@my:/home/yellowtent/platformdata/nginx/applications# ls
      default.conf  my.domain.com.conf
      root@my:/home/yellowtent/platformdata/nginx/applications# rm *
      root@my:/home/yellowtent/platformdata/nginx/applications# systemctl restart box
      

      Below is my log output

      root@my:~# journalctl -u nginx -fa
      Oct 27 19:04:54 my.domain.com nginx[1200]: nginx: [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/domain.com.host.cert": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/home/yellowtent/platformdata/nginx/cert/domain.com.host.cert, r) error:10000080:BIO routines::no such file)
      Oct 27 19:04:54 my.domain.com nginx[1200]: nginx: configuration file /etc/nginx/nginx.conf test failed
      Oct 27 19:04:54 my.domain.com systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
      Oct 27 19:04:54 my.domain.com systemd[1]: nginx.service: Failed with result 'exit-code'.
      Oct 27 19:04:54 my.domain.com systemd[1]: Failed to start A high performance web server and a reverse proxy server.
      Oct 27 19:04:54 my.domain.com systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
      Oct 27 19:04:54 my.domain.com systemd[1]: Stopped A high performance web server and a reverse proxy server.
      Oct 27 19:04:54 my.domain.com systemd[1]: nginx.service: Start request repeated too quickly.
      Oct 27 19:04:54 my.domain.com systemd[1]: nginx.service: Failed with result 'exit-code'.
      Oct 27 19:04:54 my.domain.com systemd[1]: Failed to start A high performance web server and a reverse proxy server.
      
      subvenS 1 Reply Last reply
      0
      • R roofboard

        @subven
        Thanks for the reply. Folowing the instructions.
        Here are my commands

        root@my:~# cd /home/yellowtent/platformdata/nginx/applications
        root@my:/home/yellowtent/platformdata/nginx/applications# ls
        default.conf  my.domain.com.conf
        root@my:/home/yellowtent/platformdata/nginx/applications# rm *
        root@my:/home/yellowtent/platformdata/nginx/applications# systemctl restart box
        

        Below is my log output

        root@my:~# journalctl -u nginx -fa
        Oct 27 19:04:54 my.domain.com nginx[1200]: nginx: [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/domain.com.host.cert": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/home/yellowtent/platformdata/nginx/cert/domain.com.host.cert, r) error:10000080:BIO routines::no such file)
        Oct 27 19:04:54 my.domain.com nginx[1200]: nginx: configuration file /etc/nginx/nginx.conf test failed
        Oct 27 19:04:54 my.domain.com systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
        Oct 27 19:04:54 my.domain.com systemd[1]: nginx.service: Failed with result 'exit-code'.
        Oct 27 19:04:54 my.domain.com systemd[1]: Failed to start A high performance web server and a reverse proxy server.
        Oct 27 19:04:54 my.domain.com systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
        Oct 27 19:04:54 my.domain.com systemd[1]: Stopped A high performance web server and a reverse proxy server.
        Oct 27 19:04:54 my.domain.com systemd[1]: nginx.service: Start request repeated too quickly.
        Oct 27 19:04:54 my.domain.com systemd[1]: nginx.service: Failed with result 'exit-code'.
        Oct 27 19:04:54 my.domain.com systemd[1]: Failed to start A high performance web server and a reverse proxy server.
        
        subvenS Offline
        subvenS Offline
        subven
        wrote on last edited by subven
        #6

        @roofboard please also delete certs under /home/yellowtent/platformdata/nginx/cert/ in addition to the conf at /home/yellowtent/platformdata/nginx/applications/ before restarting box service 🙂

        Not sure if you are supposed to remove nginx.conf at /home/yellowtent/platformdata/nginx/ so if you touched this file (or the mime.types), this could be an issue. In case you removed nginx.conf and mime.type as well and they are not restored by box, hit me up.

        R 1 Reply Last reply
        0
        • robiR Offline
          robiR Offline
          robi
          wrote on last edited by
          #7

          Deleting all the certs is a problem I reported recently. There may be a fix, but it's not released yet.

          Deleting all the confs is ok as they can regenerate, but not without the one cert for the main cloudron host domain.

          See what nginx is looking for? I had to generate that cert manually to get the UI back up.

          Conscious tech

          R subvenS 2 Replies Last reply
          0
          • subvenS subven

            @roofboard please also delete certs under /home/yellowtent/platformdata/nginx/cert/ in addition to the conf at /home/yellowtent/platformdata/nginx/applications/ before restarting box service 🙂

            Not sure if you are supposed to remove nginx.conf at /home/yellowtent/platformdata/nginx/ so if you touched this file (or the mime.types), this could be an issue. In case you removed nginx.conf and mime.type as well and they are not restored by box, hit me up.

            R Offline
            R Offline
            roofboard
            wrote on last edited by
            #8

            @subven
            I deleted the files in both the directories, I left the ones in /home/yellowtent/platformdata/nginx alone but inspected them (nothing unusual they are the same as other CL instances. )

            then with nginx running I ran systemctl restart box

            note - box and nginx were already running.

            If i reboot the server nginx will stop running

            and all the same my.domain.com never loads always ERR_CONNECTION_RESET

            1 Reply Last reply
            0
            • robiR robi

              Deleting all the certs is a problem I reported recently. There may be a fix, but it's not released yet.

              Deleting all the confs is ok as they can regenerate, but not without the one cert for the main cloudron host domain.

              See what nginx is looking for? I had to generate that cert manually to get the UI back up.

              R Offline
              R Offline
              roofboard
              wrote on last edited by
              #9

              @robi How do you generate certs manually?

              1 Reply Last reply
              0
              • robiR robi

                Deleting all the certs is a problem I reported recently. There may be a fix, but it's not released yet.

                Deleting all the confs is ok as they can regenerate, but not without the one cert for the main cloudron host domain.

                See what nginx is looking for? I had to generate that cert manually to get the UI back up.

                subvenS Offline
                subvenS Offline
                subven
                wrote on last edited by
                #10

                @robi hmm I remember I had a similar problem where an stopped app had no cert file which caused nginx to fail at start. I just copied and renamed a random cert to get nginx working at all. The cert for the app I was trying to fix was obviously not right but I was able to run nginx,launch the dashboard, remove the cert from the file system and trigger the renewal process from the UI. Maybe this could work too if you drop something "valid" for the dashboard domain into the nginx cert directory ^^

                R 1 Reply Last reply
                0
                • subvenS subven

                  @robi hmm I remember I had a similar problem where an stopped app had no cert file which caused nginx to fail at start. I just copied and renamed a random cert to get nginx working at all. The cert for the app I was trying to fix was obviously not right but I was able to run nginx,launch the dashboard, remove the cert from the file system and trigger the renewal process from the UI. Maybe this could work too if you drop something "valid" for the dashboard domain into the nginx cert directory ^^

                  R Offline
                  R Offline
                  roofboard
                  wrote on last edited by roofboard
                  #11

                  @subven @robi
                  ok. so we are talking about the /home/yellowtent/platformdata/nginx/cert/
                  cert folder. now i have dummy certs from another CL instance., but which files are needed in that directory? I can get them copied over.

                  I am guessing maybe... default.cert, and default.key

                  subvenS 1 Reply Last reply
                  0
                  • R roofboard

                    @subven @robi
                    ok. so we are talking about the /home/yellowtent/platformdata/nginx/cert/
                    cert folder. now i have dummy certs from another CL instance., but which files are needed in that directory? I can get them copied over.

                    I am guessing maybe... default.cert, and default.key

                    subvenS Offline
                    subvenS Offline
                    subven
                    wrote on last edited by
                    #12

                    @roofboard [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/domain.com.host.cert" start with the one that brings your nginx down ^^

                    R 1 Reply Last reply
                    0
                    • subvenS subven

                      @roofboard [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/domain.com.host.cert" start with the one that brings your nginx down ^^

                      R Offline
                      R Offline
                      roofboard
                      wrote on last edited by roofboard
                      #13

                      @subven 🤦

                      wordwrap!!! the problem was staring me in the face! But I could not see it because i did not scroll to the right...

                      Thanks for the help!!!!

                      I took a cert and key file from another server, and renamed the default cert to be whatever the error wanted.
                      first thedomain.com.cert, then thedomain.com.key. and so-forth until it loaded. It is working now! .

                      1 Reply Last reply
                      4
                      • nebulonN nebulon marked this topic as a question on
                      • nebulonN nebulon has marked this topic as solved on
                      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