[GH-ISSUE #775] Can't setup #654

Closed
opened 2026-02-26 06:33:51 +03:00 by kerem · 2 comments
Owner

Originally created by @Mylloon on GitHub (Dec 15, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/775

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    Yes

  • Are you sure you're not using someone else's docker image?
    Yes

  • If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
    My router ports are wide open.

Describe the bug

  • A clear and concise description of what the bug is.
    Everything worked fine for about 2 months, then overnight, I can no longer connect to the websites I put in proxy hosting. According to firefox, I have a probable security risk because the connection to the site is not secured. I would like to point out that everything worked well before.
    In the logs I don't notice anything abnormal except this :
    12/15/2020] [2:01:14 PM] [Nginx ] ' ℹ info Reloading Nginx

which comes back quite often.

  • What version of Nginx Proxy Manager is reported on the login page?
    v2.7.1

To Reproduce
Steps to reproduce the behavior:

  1. Go to Host, Proxy list.
  2. Add a Proxy Host.
  3. Add domain name (I use DuckDNS and it points to the right IP address) : mysubdomain.mydomain.duckdns.org.
  4. I add a local ip adress who is working x.x.x.x with the right port p.
  5. I add the right scheme, I block the common exploits.
  6. In the SSL tab I request a new SSL Certificate.
  7. I force SSL and HTTP/2 Support+.

Expected behavior
With this configuration I expect that when I go to the link subdomain.domain.duckdns.org, it points to the ip address x.x.x:p that I specified.

Operating System

  • I am using last version of OpenMediaVault, on a Pentium Dual core (E2200) @ 2.20GHz with 2 GiB of RAM with Docker and with Portainer interface.

Additional context
Here are the logs from the start of the container to the end of the step I wrote in the "Reproduce" section :

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
  ❯ /etc/nginx/conf.d/production.conf
  ❯ /etc/nginx/conf.d/include/ip_ranges.conf
  ❯ /etc/nginx/conf.d/include/force-ssl.conf
  ❯ /etc/nginx/conf.d/include/proxy.conf
  ❯ /etc/nginx/conf.d/include/block-exploits.conf
  ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
  ❯ /etc/nginx/conf.d/include/assets.conf
  ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
  ❯ /etc/nginx/conf.d/include/resolvers.conf
  ❯ /etc/nginx/conf.d/default.conf
❯ Enabling IPV6 in hosts: /data/nginx
  ❯ /data/nginx/proxy_host/1.conf
[12/15/2020] [2:16:26 PM] [Global   ] › ℹ  info      Generating MySQL db configuration from environment variables
[12/15/2020] [2:16:26 PM] [Global   ] › ℹ  info      Wrote db configuration to config file: ./config/production.json
[12/15/2020] [2:16:30 PM] [Migrate  ] › ℹ  info      Current database version: 20201014143841
[12/15/2020] [2:16:30 PM] [Setup    ] › ℹ  info      Creating a new JWT key pair...
[12/15/2020] [2:16:47 PM] [Setup    ] › ℹ  info      Wrote JWT key pair to config file: /app/config/production.json
[12/15/2020] [2:16:47 PM] [Setup    ] › ⚠  warning   Restarting interface to apply new configuration
[12/15/2020] [2:16:52 PM] [Migrate  ] › ℹ  info      Current database version: 20201014143841
[12/15/2020] [2:16:52 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[12/15/2020] [2:16:52 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[12/15/2020] [2:16:53 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[12/15/2020] [2:16:53 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[12/15/2020] [2:16:53 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[12/15/2020] [2:16:53 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[12/15/2020] [2:16:53 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[12/15/2020] [2:16:53 PM] [Global   ] › ℹ  info      Backend PID 289 listening on port 3000 ...
[12/15/2020] [2:16:58 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[12/15/2020] [2:16:58 PM] [SSL      ] › ℹ  info      Renew Complete
[12/15/2020] [2:17:12 PM] [Express  ] › ⚠  warning   invalid signature
`QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
`QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0
QueryBuilder#omit is deprecated. This method will be removed in version 3.0
[12/15/2020] [2:18:05 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[12/15/2020] [2:18:05 PM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #2: MYSUBDOMAIN.MYDOMAIN.duckdns.org
[12/15/2020] [2:18:22 PM] [SSL      ] › ✔  success   IMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/npm-2/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/npm-2/privkey.pem
   Your cert will expire on 2021-03-15. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot
   again. To non-interactively renew *all* of your certificates, run
   "certbot renew"
 - If you like Certbot, please consider supporting our work by:
   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le
[12/15/2020] [2:18:22 PM] [Nginx    ] › ℹ  info      Reloading Nginx
Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0
[12/15/2020] [2:18:23 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[12/15/2020] [2:18:23 PM] [Nginx    ] › ℹ  info      Reloading Nginx

I hope it's just me missing something and not a bug >:(

Originally created by @Mylloon on GitHub (Dec 15, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/775 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? Yes - Are you sure you're not using someone else's docker image? Yes - If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? My router ports are wide open. **Describe the bug** - A clear and concise description of what the bug is. Everything worked fine for about 2 months, then overnight, I can no longer connect to the websites I put in proxy hosting. According to firefox, I have a probable security risk because the connection to the site is not secured. I would like to point out that everything worked well before. In the logs I don't notice anything abnormal except this : 12/15/2020] [2:01:14 PM] [Nginx ] ' ℹ info Reloading Nginx which comes back quite often. - What version of Nginx Proxy Manager is reported on the login page? v2.7.1 **To Reproduce** Steps to reproduce the behavior: 1. Go to Host, Proxy list. 2. Add a Proxy Host. 3. Add domain name (I use DuckDNS and it points to the right IP address) : mysubdomain.mydomain.duckdns.org. 4. I add a local ip adress who is working x.x.x.x with the right port p. 5. I add the right scheme, I block the common exploits. 6. In the SSL tab I request a new SSL Certificate. 7. I force SSL and HTTP/2 Support+. **Expected behavior** With this configuration I expect that when I go to the link subdomain.domain.duckdns.org, it points to the ip address x.x.x:p that I specified. **Operating System** - I am using last version of OpenMediaVault, on a Pentium Dual core (E2200) @ 2.20GHz with 2 GiB of RAM with Docker and with Portainer interface. **Additional context** Here are the logs from the start of the container to the end of the step I wrote in the "Reproduce" section : ``` [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d ❯ /etc/nginx/conf.d/production.conf ❯ /etc/nginx/conf.d/include/ip_ranges.conf ❯ /etc/nginx/conf.d/include/force-ssl.conf ❯ /etc/nginx/conf.d/include/proxy.conf ❯ /etc/nginx/conf.d/include/block-exploits.conf ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf ❯ /etc/nginx/conf.d/include/assets.conf ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf ❯ /etc/nginx/conf.d/include/resolvers.conf ❯ /etc/nginx/conf.d/default.conf ❯ Enabling IPV6 in hosts: /data/nginx ❯ /data/nginx/proxy_host/1.conf [12/15/2020] [2:16:26 PM] [Global ] › ℹ info Generating MySQL db configuration from environment variables [12/15/2020] [2:16:26 PM] [Global ] › ℹ info Wrote db configuration to config file: ./config/production.json [12/15/2020] [2:16:30 PM] [Migrate ] › ℹ info Current database version: 20201014143841 [12/15/2020] [2:16:30 PM] [Setup ] › ℹ info Creating a new JWT key pair... [12/15/2020] [2:16:47 PM] [Setup ] › ℹ info Wrote JWT key pair to config file: /app/config/production.json [12/15/2020] [2:16:47 PM] [Setup ] › ⚠ warning Restarting interface to apply new configuration [12/15/2020] [2:16:52 PM] [Migrate ] › ℹ info Current database version: 20201014143841 [12/15/2020] [2:16:52 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [12/15/2020] [2:16:52 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [12/15/2020] [2:16:53 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [12/15/2020] [2:16:53 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [12/15/2020] [2:16:53 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [12/15/2020] [2:16:53 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [12/15/2020] [2:16:53 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [12/15/2020] [2:16:53 PM] [Global ] › ℹ info Backend PID 289 listening on port 3000 ... [12/15/2020] [2:16:58 PM] [Nginx ] › ℹ info Reloading Nginx [12/15/2020] [2:16:58 PM] [SSL ] › ℹ info Renew Complete [12/15/2020] [2:17:12 PM] [Express ] › ⚠ warning invalid signature `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0 `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0 QueryBuilder#omit is deprecated. This method will be removed in version 3.0 [12/15/2020] [2:18:05 PM] [Nginx ] › ℹ info Reloading Nginx [12/15/2020] [2:18:05 PM] [SSL ] › ℹ info Requesting Let'sEncrypt certificates for Cert #2: MYSUBDOMAIN.MYDOMAIN.duckdns.org [12/15/2020] [2:18:22 PM] [SSL ] › ✔ success IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/npm-2/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/npm-2/privkey.pem Your cert will expire on 2021-03-15. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run "certbot renew" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le [12/15/2020] [2:18:22 PM] [Nginx ] › ℹ info Reloading Nginx Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0 [12/15/2020] [2:18:23 PM] [Nginx ] › ℹ info Reloading Nginx [12/15/2020] [2:18:23 PM] [Nginx ] › ℹ info Reloading Nginx ``` I hope it's just me missing something and not a bug >:(
kerem 2026-02-26 06:33:51 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@Mylloon commented on GitHub (Dec 15, 2020):

I can maybe add this screenshot from firefox, sorry it's written in french.

image

<!-- gh-comment-id:745320424 --> @Mylloon commented on GitHub (Dec 15, 2020): I can maybe add this screenshot from firefox, sorry it's written in french. ![image](https://user-images.githubusercontent.com/29067904/102227347-be8ac680-3ee9-11eb-8795-0fccce357d9d.png)
Author
Owner

@Mylloon commented on GitHub (Dec 17, 2020):

Update: Well, I didn't do anything and it was repaired by itself, I'm lucky I guess ...

<!-- gh-comment-id:747500144 --> @Mylloon commented on GitHub (Dec 17, 2020): Update: Well, I didn't do anything and it was repaired by itself, I'm lucky I guess ...
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#654
No description provided.