NGINX Proxymanage Certifikate erneuern schlägt fehl
-
Hi,
Aus welchem Grund auch immer werden meine Certs auf dem NGINX Reverse Proxy nicht mehr erneuert und mir gehen die Ideen aus.
NGINX läuft (noch) im Docker Container (Portainer) unter Proxmox CT.
Einrichtung hat seinerzeit Problemlos funktioniert. Jetzt erhalte ich seit Tagen die Meldungen das die Certs auslaufen und wollte mir das mal ansehen. Komme aber leider gerade nicht weiter.
Habe schon alles mehrfach neu gestartet, Container neu erstellt, VM aus Backup restored usw. Geht trotzdem nicht.
FB stellt den Internetzugang, dahinter alle Unifi.
Unifi:
Container log:
s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/01_perms.sh /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: 20: /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: /etc/cont-init.d/01_perms.sh: not found cont-init: info: /etc/cont-init.d/01_perms.sh exited 127 cont-init: info: running /etc/cont-init.d/01_s6-secret-init.sh /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: 20: /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: /etc/cont-init.d/01_s6-secret-init.sh: Permission denied cont-init: info: /etc/cont-init.d/01_s6-secret-init.sh exited 126 cont-init: warning: some scripts exited nonzero ❯ Checking folder structure ... s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service prepare: starting ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d ❯ /etc/nginx/conf.d/default.conf ❯ /etc/nginx/conf.d/production.conf ❯ /etc/nginx/conf.d/include/assets.conf ❯ /etc/nginx/conf.d/include/force-ssl.conf ❯ /etc/nginx/conf.d/include/block-exploits.conf ❯ /etc/nginx/conf.d/include/ip_ranges.conf ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf ❯ /etc/nginx/conf.d/include/proxy.conf ❯ /etc/nginx/conf.d/include/resolvers.conf ❯ Enabling IPV6 in hosts: /data/nginx ❯ /data/nginx/proxy_host/3.conf ❯ /data/nginx/proxy_host/2.conf s6-rc: info: service prepare successfully started s6-rc: info: service nginx: starting s6-rc: info: service frontend: starting s6-rc: info: service backend: starting ------------------------------------- _ _ ____ __ __ | \ | | _ \| \/ | | \| | |_) | |\/| | | |\ | __/| | | | |_| \_|_| |_| |_| ------------------------------------- s6-rc: info: service nginx successfully started s6-rc: info: service frontend successfully started ❯ Starting nginx ... s6-rc: info: service backend successfully started ❯ Starting backend ... s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [3/19/2023] [12:51:45 PM] [Global ] › ℹ info Manual db configuration already exists, skipping config creation from environment variables [3/19/2023] [12:51:46 PM] [Migrate ] › ℹ info Current database version: 20211108145214 [3/19/2023] [12:51:47 PM] [Setup ] › ℹ info Logrotate Timer initialized [3/19/2023] [12:51:47 PM] [Setup ] › ℹ info Logrotate completed. [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [3/19/2023] [12:51:47 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [3/19/2023] [12:51:47 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [3/19/2023] [12:51:47 PM] [Global ] › ℹ info Backend PID 104 listening on port 3000 ... [3/19/2023] [12:52:55 PM] [SSL ] › ℹ info Testing http challenge for dxxxxxxxy.com Uncaught SyntaxError: Unexpected end of JSON input FROM ./run: line 19: 104 Trace/breakpoint trap (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ❯ Starting backend ... [3/19/2023] [12:52:57 PM] [Global ] › ℹ info Manual db configuration already exists, skipping config creation from environment variables [3/19/2023] [12:52:59 PM] [Migrate ] › ℹ info Current database version: 20211108145214 [3/19/2023] [12:52:59 PM] [Setup ] › ℹ info Logrotate Timer initialized [3/19/2023] [12:52:59 PM] [Setup ] › ℹ info Logrotate completed. [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [3/19/2023] [12:52:59 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [3/19/2023] [12:52:59 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [3/19/2023] [12:52:59 PM] [Global ] › ℹ info Backend PID 360 listening on port 3000 ... [3/19/2023] [12:53:00 PM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation Another instance of Certbot is already running. at ChildProcess.exithandler (node:child_process:402:12) at ChildProcess.emit (node:events:513:28) at maybeClose (node:internal/child_process:1100:16) at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)"Another instance of Certbot..." kommt sobald ich den Verbindungstest ausgeführt habe:
Browser Log:
Hat zufällig jemand eine Idee?
Bitte keine Fragen per PN, die gehören ins Forum!
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
-
Hi,
Aus welchem Grund auch immer werden meine Certs auf dem NGINX Reverse Proxy nicht mehr erneuert und mir gehen die Ideen aus.
NGINX läuft (noch) im Docker Container (Portainer) unter Proxmox CT.
Einrichtung hat seinerzeit Problemlos funktioniert. Jetzt erhalte ich seit Tagen die Meldungen das die Certs auslaufen und wollte mir das mal ansehen. Komme aber leider gerade nicht weiter.
Habe schon alles mehrfach neu gestartet, Container neu erstellt, VM aus Backup restored usw. Geht trotzdem nicht.
FB stellt den Internetzugang, dahinter alle Unifi.
Unifi:
Container log:
s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/01_perms.sh /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: 20: /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: /etc/cont-init.d/01_perms.sh: not found cont-init: info: /etc/cont-init.d/01_perms.sh exited 127 cont-init: info: running /etc/cont-init.d/01_s6-secret-init.sh /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: 20: /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: /etc/cont-init.d/01_s6-secret-init.sh: Permission denied cont-init: info: /etc/cont-init.d/01_s6-secret-init.sh exited 126 cont-init: warning: some scripts exited nonzero ❯ Checking folder structure ... s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service prepare: starting ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d ❯ /etc/nginx/conf.d/default.conf ❯ /etc/nginx/conf.d/production.conf ❯ /etc/nginx/conf.d/include/assets.conf ❯ /etc/nginx/conf.d/include/force-ssl.conf ❯ /etc/nginx/conf.d/include/block-exploits.conf ❯ /etc/nginx/conf.d/include/ip_ranges.conf ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf ❯ /etc/nginx/conf.d/include/proxy.conf ❯ /etc/nginx/conf.d/include/resolvers.conf ❯ Enabling IPV6 in hosts: /data/nginx ❯ /data/nginx/proxy_host/3.conf ❯ /data/nginx/proxy_host/2.conf s6-rc: info: service prepare successfully started s6-rc: info: service nginx: starting s6-rc: info: service frontend: starting s6-rc: info: service backend: starting ------------------------------------- _ _ ____ __ __ | \ | | _ \| \/ | | \| | |_) | |\/| | | |\ | __/| | | | |_| \_|_| |_| |_| ------------------------------------- s6-rc: info: service nginx successfully started s6-rc: info: service frontend successfully started ❯ Starting nginx ... s6-rc: info: service backend successfully started ❯ Starting backend ... s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [3/19/2023] [12:51:45 PM] [Global ] › ℹ info Manual db configuration already exists, skipping config creation from environment variables [3/19/2023] [12:51:46 PM] [Migrate ] › ℹ info Current database version: 20211108145214 [3/19/2023] [12:51:47 PM] [Setup ] › ℹ info Logrotate Timer initialized [3/19/2023] [12:51:47 PM] [Setup ] › ℹ info Logrotate completed. [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [3/19/2023] [12:51:47 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [3/19/2023] [12:51:47 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [3/19/2023] [12:51:47 PM] [Global ] › ℹ info Backend PID 104 listening on port 3000 ... [3/19/2023] [12:52:55 PM] [SSL ] › ℹ info Testing http challenge for dxxxxxxxy.com Uncaught SyntaxError: Unexpected end of JSON input FROM ./run: line 19: 104 Trace/breakpoint trap (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ❯ Starting backend ... [3/19/2023] [12:52:57 PM] [Global ] › ℹ info Manual db configuration already exists, skipping config creation from environment variables [3/19/2023] [12:52:59 PM] [Migrate ] › ℹ info Current database version: 20211108145214 [3/19/2023] [12:52:59 PM] [Setup ] › ℹ info Logrotate Timer initialized [3/19/2023] [12:52:59 PM] [Setup ] › ℹ info Logrotate completed. [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [3/19/2023] [12:52:59 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [3/19/2023] [12:52:59 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [3/19/2023] [12:52:59 PM] [Global ] › ℹ info Backend PID 360 listening on port 3000 ... [3/19/2023] [12:53:00 PM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation Another instance of Certbot is already running. at ChildProcess.exithandler (node:child_process:402:12) at ChildProcess.emit (node:events:513:28) at maybeClose (node:internal/child_process:1100:16) at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)"Another instance of Certbot..." kommt sobald ich den Verbindungstest ausgeführt habe:
Browser Log:
Hat zufällig jemand eine Idee?
@wendy2702 Idee keine aber
--preferred-challenges "dns,http"willst du vermutlich nicht, da sollte nurhttpstehen, DNS ist etwas komplizierter.Ansonsten scheinst du die Ports 80 und 443 von außen bis an den Container durchgereicht zu haben.
Den Container schon mal neu gestartet? Wann versucht er denn das erneuern?
Eventuell ist auch eine aktuellere Certbot-Version notwendig, die Befehlszeile die du da siehts kannst du auch von Hand ausführen, alsocertbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validationWenn du dann das
--quietweglässt gibt es eventuell mehr infos.ioBroker@Ubuntu 24.04 LTS (VMware) für: >260 Geräte, 5 Switche, 7 AP, 10 IP-Cam, 1 NAS 42TB, 1 ESXi 15TB, 4 Proxmox 1TB, 1 Hyper-V 48TB, 14 x Echo, 5x FireTV, 5 x Tablett/Handy VIS || >=160 Tasmota/Shelly || >=95 ZigBee || PV 8.1kW / Akku 14kWh || 2x USV APC 750W kaskadiert || Creality CR-10 SE 3D-Drucker
-
@wendy2702 Idee keine aber
--preferred-challenges "dns,http"willst du vermutlich nicht, da sollte nurhttpstehen, DNS ist etwas komplizierter.Ansonsten scheinst du die Ports 80 und 443 von außen bis an den Container durchgereicht zu haben.
Den Container schon mal neu gestartet? Wann versucht er denn das erneuern?
Eventuell ist auch eine aktuellere Certbot-Version notwendig, die Befehlszeile die du da siehts kannst du auch von Hand ausführen, alsocertbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validationWenn du dann das
--quietweglässt gibt es eventuell mehr infos.@bananajoe Danke für deine Antwort.
@bananajoe sagte in NGINX Proxymanage Certifikate erneuern schlägt fehl:
Den Container schon mal neu gestartet? Wann versucht er denn das erneuern?
Mehrfach versucht. Auch den Container schon recreate mit latest Template.
Leider ist das Log zwar etwas informativer aber es gibt wohl laut Google keinen wirklichen Fix.
Ich habe letztendlich das hier gemacht:
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/396#issuecomment-1077966420
Muss mal in Ruhe schauen ob es eine Dauerhafte Lösung gibt oder ich das mit dem NPM anders lösen kann.
-
Hi,
Aus welchem Grund auch immer werden meine Certs auf dem NGINX Reverse Proxy nicht mehr erneuert und mir gehen die Ideen aus.
NGINX läuft (noch) im Docker Container (Portainer) unter Proxmox CT.
Einrichtung hat seinerzeit Problemlos funktioniert. Jetzt erhalte ich seit Tagen die Meldungen das die Certs auslaufen und wollte mir das mal ansehen. Komme aber leider gerade nicht weiter.
Habe schon alles mehrfach neu gestartet, Container neu erstellt, VM aus Backup restored usw. Geht trotzdem nicht.
FB stellt den Internetzugang, dahinter alle Unifi.
Unifi:
Container log:
s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/01_perms.sh /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: 20: /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: /etc/cont-init.d/01_perms.sh: not found cont-init: info: /etc/cont-init.d/01_perms.sh exited 127 cont-init: info: running /etc/cont-init.d/01_s6-secret-init.sh /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: 20: /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: /etc/cont-init.d/01_s6-secret-init.sh: Permission denied cont-init: info: /etc/cont-init.d/01_s6-secret-init.sh exited 126 cont-init: warning: some scripts exited nonzero ❯ Checking folder structure ... s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service prepare: starting ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d ❯ /etc/nginx/conf.d/default.conf ❯ /etc/nginx/conf.d/production.conf ❯ /etc/nginx/conf.d/include/assets.conf ❯ /etc/nginx/conf.d/include/force-ssl.conf ❯ /etc/nginx/conf.d/include/block-exploits.conf ❯ /etc/nginx/conf.d/include/ip_ranges.conf ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf ❯ /etc/nginx/conf.d/include/proxy.conf ❯ /etc/nginx/conf.d/include/resolvers.conf ❯ Enabling IPV6 in hosts: /data/nginx ❯ /data/nginx/proxy_host/3.conf ❯ /data/nginx/proxy_host/2.conf s6-rc: info: service prepare successfully started s6-rc: info: service nginx: starting s6-rc: info: service frontend: starting s6-rc: info: service backend: starting ------------------------------------- _ _ ____ __ __ | \ | | _ \| \/ | | \| | |_) | |\/| | | |\ | __/| | | | |_| \_|_| |_| |_| ------------------------------------- s6-rc: info: service nginx successfully started s6-rc: info: service frontend successfully started ❯ Starting nginx ... s6-rc: info: service backend successfully started ❯ Starting backend ... s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [3/19/2023] [12:51:45 PM] [Global ] › ℹ info Manual db configuration already exists, skipping config creation from environment variables [3/19/2023] [12:51:46 PM] [Migrate ] › ℹ info Current database version: 20211108145214 [3/19/2023] [12:51:47 PM] [Setup ] › ℹ info Logrotate Timer initialized [3/19/2023] [12:51:47 PM] [Setup ] › ℹ info Logrotate completed. [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [3/19/2023] [12:51:47 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [3/19/2023] [12:51:47 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [3/19/2023] [12:51:47 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [3/19/2023] [12:51:47 PM] [Global ] › ℹ info Backend PID 104 listening on port 3000 ... [3/19/2023] [12:52:55 PM] [SSL ] › ℹ info Testing http challenge for dxxxxxxxy.com Uncaught SyntaxError: Unexpected end of JSON input FROM ./run: line 19: 104 Trace/breakpoint trap (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ❯ Starting backend ... [3/19/2023] [12:52:57 PM] [Global ] › ℹ info Manual db configuration already exists, skipping config creation from environment variables [3/19/2023] [12:52:59 PM] [Migrate ] › ℹ info Current database version: 20211108145214 [3/19/2023] [12:52:59 PM] [Setup ] › ℹ info Logrotate Timer initialized [3/19/2023] [12:52:59 PM] [Setup ] › ℹ info Logrotate completed. [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [3/19/2023] [12:52:59 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [3/19/2023] [12:52:59 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [3/19/2023] [12:52:59 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [3/19/2023] [12:52:59 PM] [Global ] › ℹ info Backend PID 360 listening on port 3000 ... [3/19/2023] [12:53:00 PM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation Another instance of Certbot is already running. at ChildProcess.exithandler (node:child_process:402:12) at ChildProcess.emit (node:events:513:28) at maybeClose (node:internal/child_process:1100:16) at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)"Another instance of Certbot..." kommt sobald ich den Verbindungstest ausgeführt habe:
Browser Log:
Hat zufällig jemand eine Idee?
@wendy2702
Welches release des NPM ist installiert? Es gab in den letzten vier Tagen zwei Aktualisierungen. Aktuell ist 2.9.21.Proxmox und HA
-
@wendy2702
Welches release des NPM ist installiert? Es gab in den letzten vier Tagen zwei Aktualisierungen. Aktuell ist 2.9.21.@meister-mopper Noch 2.9.19
Mal update machen.
Support us
560
Online32.7k
Users82.4k
Topics1.3m
Posts