NGINX stopped suddenly to function on Docker Qnap

Post Reply
PaulP5
New here
Posts: 2
Joined: Fri Sep 07, 2018 6:05 pm

NGINX stopped suddenly to function on Docker Qnap

Post by PaulP5 »

Hello,
I'am facing problems with the NGINX-server (Jlesage) since a month.
NGINX functioned well for more than a year . A month ago suddenly the home-assistant webhook for the Netatmocamera didn't work anymore. After some examination NGINX is the cause. Reinstallation of the container, NGINX, ... didn't help.

Environment:
Qnap TS253A QTS 4.5.4.1741 Container Docker
NGINX install command:
docker run -d --name="nginx-proxy-manager" -p 443:4443 -p 80:8080 -p 8181:8181 -v /share/container/nginx-proxy-manager:/config:rw -e TZ=Europe/Brussels jlesage/nginx-proxy-manager

Image:
jlesage/nginx-proxy-manager:latest

Result:
Schermafbeelding 2021-09-17 om 11.31.27.png
Each time the port forwarding is refused. Also when I use the UI, after "APPLY" the ports are gone .
Why ?

Console messages:
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-app-niceness.sh: executing...
[cont-init.d] 00-app-niceness.sh: exited 0.
[cont-init.d] 00-app-script.sh: executing...
[cont-init.d] 00-app-script.sh: exited 0.
[cont-init.d] 00-app-user-map.sh: executing...
[cont-init.d] 00-app-user-map.sh: exited 0.
[cont-init.d] 00-clean-logmonitor-states.sh: executing...
[cont-init.d] 00-clean-logmonitor-states.sh: exited 0.
[cont-init.d] 00-clean-tmp-dir.sh: executing...
[cont-init.d] 00-clean-tmp-dir.sh: exited 0.
[cont-init.d] 00-set-app-deps.sh: executing...
[cont-init.d] 00-set-app-deps.sh: exited 0.
[cont-init.d] 00-set-home.sh: executing...
[cont-init.d] 00-set-home.sh: exited 0.
[cont-init.d] 00-take-config-ownership.sh: executing...
[cont-init.d] 00-take-config-ownership.sh: exited 0.
[cont-init.d] 00-xdg-runtime-dir.sh: executing...
[cont-init.d] 00-xdg-runtime-dir.sh: exited 0.
[cont-init.d] 90-db-upgrade.sh: executing...
[cont-init.d] 90-db-upgrade.sh: exited 0.
[cont-init.d] nginx-proxy-manager.sh: executing...
❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
❯ /etc/nginx/conf.d/default.conf
❯ /etc/nginx/conf.d/include/assets.conf
❯ /etc/nginx/conf.d/include/block-exploits.conf
❯ /etc/nginx/conf.d/include/force-ssl.conf
❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
❯ /etc/nginx/conf.d/include/proxy.conf
❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
❯ /etc/nginx/conf.d/production.conf
❯ Enabling IPV6 in hosts: /config/nginx
❯ /config/nginx/proxy_host/1.conf
❯ /config/nginx/ip_ranges.conf
❯ /config/nginx/resolvers.conf
chown: /config/log/log: Symbolic link loop
[cont-init.d] nginx-proxy-manager.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] starting s6-fdholderd...
[services.d] starting cert_cleanup...
[cert_cleanup] starting...
[services.d] starting logmonitor...
[services.d] starting nginx...
[nginx] starting...
[services.d] starting statusmonitor...
[services.d] starting app...
[statusmonitor] no file to monitor: disabling service...
[logmonitor] no file to monitor: disabling service...
[app] starting Nginx Proxy Manager...
[services.d] done.
[cert_cleanup] ----------------------------------------------------------
[cert_cleanup] Let's Encrypt certificates cleanup - 2021/09/17 11:06:32
[cert_cleanup] ----------------------------------------------------------
[cert_cleanup] Keeping /etc/letsencrypt/archive/npm-1/cert1.pem.
[cert_cleanup] Keeping /etc/letsencrypt/archive/npm-1/privkey1.pem.
[cert_cleanup] Keeping /etc/letsencrypt/archive/npm-1/chain1.pem.
[cert_cleanup] Keeping /etc/letsencrypt/archive/npm-1/fullchain1.pem.
[cert_cleanup] 4 file(s) kept.
[cert_cleanup] 0 file(s) deleted.
[9/17/2021] [11:06:41 AM] [Migrate ] › ℹ info Current database version: none
[9/17/2021] [11:06:42 AM] [Setup ] › ℹ info Logrotate Timer initialized
[9/17/2021] [11:06:42 AM] [Setup ] › ℹ info Logrotate completed.
[9/17/2021] [11:06:42 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services...
[9/17/2021] [11:06:42 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[9/17/2021] [11:06:43 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4
[9/17/2021] [11:06:43 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6
[9/17/2021] [11:06:43 AM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized
[9/17/2021] [11:06:43 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[9/17/2021] [11:06:43 AM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized
[9/17/2021] [11:06:43 AM] [Global ] › ℹ info Backend PID 832 listening on port 3000 ...
[9/17/2021] [11:06:48 AM] [Nginx ] › ℹ info Reloading Nginx
[9/17/2021] [11:06:48 AM] [SSL ] › ℹ info Renew Complete

What is the cause and .. solution?

Thx very much for your help.

Paulp
You do not have the required permissions to view the files attached to this post.
User avatar
oyvindo
Experience counts
Posts: 1399
Joined: Tue May 19, 2009 2:08 am
Location: Norway, Oslo

Re: NGINX stopped suddenly to function on Docker Qnap

Post by oyvindo »

Did you check the Netatmo developer page if your API account has been banned?
This happens after too many repeated failed attempt to connect, and you have manually release the ban.
ImageImageImage
PaulP5
New here
Posts: 2
Joined: Fri Sep 07, 2018 6:05 pm

Re: NGINX stopped suddenly to function on Docker Qnap

Post by PaulP5 »

API has not been banned. Still active.
Post Reply

Return to “Container Station”