Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nginx: [emerg] cannot load certificate at start #602

Open
txf- opened this issue Sep 24, 2024 · 1 comment
Open

nginx: [emerg] cannot load certificate at start #602

txf- opened this issue Sep 24, 2024 · 1 comment

Comments

@txf-
Copy link

txf- commented Sep 24, 2024

Problem/Motivation

I cannot start Nginx Proxy Manager

Expected behavior

Start the service. Or at least a way to reset the the configuration so that it doesn't look for the missing files. Uninstalling and reinstalling does eliminate the problem.

Actual behavior

It starts then stops, there seems to be problem with a missing lets encrypt *.pem file:

Add-on: Nginx Proxy Manager
 Manage Nginx proxy hosts with a simple, powerful interface
-----------------------------------------------------------
 Add-on version: 1.0.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.2  (aarch64 / yellow)
 Home Assistant Core: 2024.9.2
 Home Assistant Supervisor: 2024.09.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-npm: starting
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-npm successfully started
s6-rc: info: service npm: starting
s6-rc: info: service npm successfully started
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
[23:13:43] INFO: Starting the Manager...
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
[23:13:43] INFO: Starting NGinx...
s6-rc: info: service legacy-services successfully started
nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-2/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/etc/letsencrypt/live/npm-2/fullchain.pem, r) error:10000080:BIO routines::no such file)
[23:13:44] INFO: Service NGINX exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service npm: stopping
s6-rc: info: service init-nginx successfully stopped
[23:13:44] INFO: Service Nginx Proxy Manager exited with code 256 (by signal 15)
s6-rc: info: service npm successfully stopped
s6-rc: info: service init-npm: stopping
s6-rc: info: service init-npm successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Steps to reproduce

I do not know exactly what caused it. I had deleted a ssl entry via the management page.

@MrEbbinghaus
Copy link

I guess the issue is that you still have the host config, that expects the certificate.

Look into /addon_configs/a0d7b954_nginxproxymanager/nginx/proxy_host/ (or the other host directories redirection_host/ and dead_host/) and delete the config that has the line ssl_certificate /etc/letsencrypt/live/npm-2/fullchain.pem;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants