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. Inaccessible because of expired certificates

Inaccessible because of expired certificates

Scheduled Pinned Locked Moved Solved Support
10 Posts 3 Posters 1.5k 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.
    • rosanoR Offline
      rosanoR Offline
      rosano
      wrote on last edited by
      #1

      Two of my Ghost installations are not accessible because of expired certificates, and it seems the Cloudron installation is also not accessible for the same reason. How can I resolve this?

      BrutalBirdieB 1 Reply Last reply
      0
      • rosanoR rosano

        @nebulon said in Inaccessible because of expired certificates:

        remove the nginx configs for those two apps

        How do I do this?

        @nebulon said in Inaccessible because of expired certificates:

        Afterwards re-save the location setting of the ghost instances through the Cloudron dashboard (or hit repair depending on its state) to rebuild the nginx config for it.

        I had re-booted the droplet and can't seem to access the dashboard anymore, but maybe the first thing will resolve that?

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

        @rosano the filest are in /etc/nginx/applications/ you may have to grep through those files to find the ones which are faulty and then remove them until a systemctl retart nginx succeeds. The files can be traced by looking at the nginx start error logs.

        rosanoR 1 Reply Last reply
        0
        • rosanoR rosano

          Two of my Ghost installations are not accessible because of expired certificates, and it seems the Cloudron installation is also not accessible for the same reason. How can I resolve this?

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

          @rosano could it be that you got hit by the infamous out-of-space issue?

          https://forum.cloudron.io/topic/7153/out-of-space-error-leading-to-missing-certs

          Like my work? Consider donating a drink. Cheers!

          1 Reply Last reply
          0
          • rosanoR Offline
            rosanoR Offline
            rosano
            wrote on last edited by
            #3

            I am getting some kind of nginx error but i think it's different

            Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: Starting nginx - high performance web server...
            Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 nginx[6173]: nginx: [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/chat.0data.app.cert": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/home/yellowtent/platformdata/nginx/cert/chat.0data.app.cert','r') error:2006D080:BIO routines:BIO_new_file:no such file)
            Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
            Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Failed with result 'exit-code'.
            Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: Failed to start nginx - high performance web server.
            Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
            Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: Stopped nginx - high performance web server.
            Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Start request repeated too quickly.
            Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Failed with result 'exit-code'.
            Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: Failed to start nginx - high performance web server.
            
            nebulonN BrutalBirdieB 2 Replies Last reply
            0
            • nebulonN nebulon marked this topic as a question on
            • rosanoR Offline
              rosanoR Offline
              rosano
              wrote on last edited by
              #4

              FYI there's a typo at journactl here https://docs.cloudron.io/troubleshooting/#nginx-error

              (sorry I can't figure out how to sign into your GitLab)

              1 Reply Last reply
              0
              • rosanoR rosano

                I am getting some kind of nginx error but i think it's different

                Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: Starting nginx - high performance web server...
                Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 nginx[6173]: nginx: [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/chat.0data.app.cert": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/home/yellowtent/platformdata/nginx/cert/chat.0data.app.cert','r') error:2006D080:BIO routines:BIO_new_file:no such file)
                Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
                Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Failed with result 'exit-code'.
                Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: Failed to start nginx - high performance web server.
                Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
                Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: Stopped nginx - high performance web server.
                Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Start request repeated too quickly.
                Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Failed with result 'exit-code'.
                Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: Failed to start nginx - high performance web server.
                
                nebulonN Offline
                nebulonN Offline
                nebulon
                Staff
                wrote on last edited by
                #5

                @rosano were those apps possibly stopped for some time? There was a bug in previous versions, where this happened for stopped apps. In your case SSH into the server and remove the nginx configs for those two apps, then it should be able to start again. Afterwards re-save the location setting of the ghost instances through the Cloudron dashboard (or hit repair depending on its state) to rebuild the nginx config for it.

                rosanoR 1 Reply Last reply
                0
                • nebulonN nebulon

                  @rosano were those apps possibly stopped for some time? There was a bug in previous versions, where this happened for stopped apps. In your case SSH into the server and remove the nginx configs for those two apps, then it should be able to start again. Afterwards re-save the location setting of the ghost instances through the Cloudron dashboard (or hit repair depending on its state) to rebuild the nginx config for it.

                  rosanoR Offline
                  rosanoR Offline
                  rosano
                  wrote on last edited by
                  #6

                  @nebulon said in Inaccessible because of expired certificates:

                  remove the nginx configs for those two apps

                  How do I do this?

                  @nebulon said in Inaccessible because of expired certificates:

                  Afterwards re-save the location setting of the ghost instances through the Cloudron dashboard (or hit repair depending on its state) to rebuild the nginx config for it.

                  I had re-booted the droplet and can't seem to access the dashboard anymore, but maybe the first thing will resolve that?

                  nebulonN 1 Reply Last reply
                  0
                  • rosanoR rosano

                    @nebulon said in Inaccessible because of expired certificates:

                    remove the nginx configs for those two apps

                    How do I do this?

                    @nebulon said in Inaccessible because of expired certificates:

                    Afterwards re-save the location setting of the ghost instances through the Cloudron dashboard (or hit repair depending on its state) to rebuild the nginx config for it.

                    I had re-booted the droplet and can't seem to access the dashboard anymore, but maybe the first thing will resolve that?

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

                    @rosano the filest are in /etc/nginx/applications/ you may have to grep through those files to find the ones which are faulty and then remove them until a systemctl retart nginx succeeds. The files can be traced by looking at the nginx start error logs.

                    rosanoR 1 Reply Last reply
                    0
                    • rosanoR rosano

                      I am getting some kind of nginx error but i think it's different

                      Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: Starting nginx - high performance web server...
                      Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 nginx[6173]: nginx: [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/chat.0data.app.cert": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/home/yellowtent/platformdata/nginx/cert/chat.0data.app.cert','r') error:2006D080:BIO routines:BIO_new_file:no such file)
                      Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
                      Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Failed with result 'exit-code'.
                      Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: Failed to start nginx - high performance web server.
                      Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
                      Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: Stopped nginx - high performance web server.
                      Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Start request repeated too quickly.
                      Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: nginx.service: Failed with result 'exit-code'.
                      Jun 09 07:24:43 cloudron-ubuntu-s-1vcpu-1gb-nyc1-01 systemd[1]: Failed to start nginx - high performance web server.
                      
                      BrutalBirdieB Offline
                      BrutalBirdieB Offline
                      BrutalBirdie
                      Partner
                      wrote on last edited by BrutalBirdie
                      #8

                      @rosano Did you check if you are running out of space?


                      Edit: ignore this.
                      The forum did not update the view in time and I did not see the other responses.

                      Like my work? Consider donating a drink. Cheers!

                      rosanoR 1 Reply Last reply
                      0
                      • nebulonN nebulon

                        @rosano the filest are in /etc/nginx/applications/ you may have to grep through those files to find the ones which are faulty and then remove them until a systemctl retart nginx succeeds. The files can be traced by looking at the nginx start error logs.

                        rosanoR Offline
                        rosanoR Offline
                        rosano
                        wrote on last edited by
                        #9

                        @nebulon ok I was able to grep 0data * to find the file with chat.0data.app and deleted it, then ran systemctl restart nginx without issue. All is good.

                        1 Reply Last reply
                        0
                        • rosanoR rosano has marked this topic as solved on
                        • BrutalBirdieB BrutalBirdie

                          @rosano Did you check if you are running out of space?


                          Edit: ignore this.
                          The forum did not update the view in time and I did not see the other responses.

                          rosanoR Offline
                          rosanoR Offline
                          rosano
                          wrote on last edited by
                          #10

                          @BrutalBirdie I did also check but I think I'm at 60% of capacity.

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