Solved Inaccessible because of expired certificates

[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?

[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.

[BrutalBirdie]

@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

[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.

[rosano]

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)

[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.

[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?

[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.

[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.

[rosano]

@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.

[rosano]

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