starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #392] Invalid ipv6 resolver address #333

New issue
Closed
opened 2026-02-26 06:32:21 +03:00 by kerem · 10 comments
kerem commented 2026-02-26 06:32:21 +03:00
Owner
Copy link

Originally created by @tknx on GitHub (May 2, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/392

Updated to latest docker recently and now the docker won't launch.

  • A clear and concise description of what the bug is.

Logs show the following error:

[nginx] starting...
nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1
  • What version of Nginx Proxy Manager is reported on the login page?

Can't see but just updated

Operating System

  • Unraid (Slackware)

Additional context

I tried removing the offending address directly from the conf file but it seemed to add it back

Originally created by @tknx on GitHub (May 2, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/392 Updated to latest docker recently and now the docker won't launch. - A clear and concise description of what the bug is. Logs show the following error: ``` [nginx] starting... nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1 ``` - What version of Nginx Proxy Manager is reported on the login page? Can't see but just updated **Operating System** - Unraid (Slackware) **Additional context** I tried removing the offending address directly from the conf file but it seemed to add it back
kerem 2026-02-26 06:32:21 +03:00
  • closed this issue
  • added the
    stale
    bug
         labels
kerem commented 2026-02-26 06:32:22 +03:00
Author
Owner
Copy link

@tknx commented on GitHub (May 2, 2020):

Excerpt from logs here:

Version: '10.3.22-MariaDB' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server

[services.d] starting nginx...
[services.d] starting app...
[nginx] starting...
[app] starting Nginx Proxy Manager...
[services.d] done.
nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1
[nginx] starting...
nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1
[5/2/2020] [9:30:39 AM] [Migrate ] › ℹ info Current database version: 20200410143839

[5/2/2020] [9:30:39 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services...
[5/2/2020] [9:30:39 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[nginx] starting...
nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1
[5/2/2020] [9:30:39 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4
[5/2/2020] [9:30:39 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6
[5/2/2020] [9:30:39 AM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized
[5/2/2020] [9:30:39 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[5/2/2020] [9:30:39 AM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized
[5/2/2020] [9:30:39 AM] [Global ] › ℹ info Backend PID 1645 listening on port 3000 ...
[nginx] starting...
nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1
[nginx] starting...
nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1
[nginx] starting...
nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1
[5/2/2020] [9:30:42 AM] [SSL ] › ✖ error Error: Command failed: /usr/sbin/nginx -t

nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1
nginx: configuration file /etc/nginx/nginx.conf test failed


at ChildProcess.exithandler (child_process.js:294:12)
at ChildProcess.emit (events.js:182:13)
at maybeClose (internal/child_process.js:962:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
[nginx] starting...
nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1
[nginx] starting...
nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1
[nginx] starting...
nginx: [emerg] invalid
<!-- gh-comment-id:622980232 --> @tknx commented on GitHub (May 2, 2020): Excerpt from logs here: ``` Version: '10.3.22-MariaDB' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server [services.d] starting nginx... [services.d] starting app... [nginx] starting... [app] starting Nginx Proxy Manager... [services.d] done. nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1 [nginx] starting... nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1 [5/2/2020] [9:30:39 AM] [Migrate ] › ℹ info Current database version: 20200410143839 [5/2/2020] [9:30:39 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [5/2/2020] [9:30:39 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [nginx] starting... nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1 [5/2/2020] [9:30:39 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [5/2/2020] [9:30:39 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [5/2/2020] [9:30:39 AM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [5/2/2020] [9:30:39 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [5/2/2020] [9:30:39 AM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [5/2/2020] [9:30:39 AM] [Global ] › ℹ info Backend PID 1645 listening on port 3000 ... [nginx] starting... nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1 [nginx] starting... nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1 [nginx] starting... nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1 [5/2/2020] [9:30:42 AM] [SSL ] › ✖ error Error: Command failed: /usr/sbin/nginx -t nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1 nginx: configuration file /etc/nginx/nginx.conf test failed at ChildProcess.exithandler (child_process.js:294:12) at ChildProcess.emit (events.js:182:13) at maybeClose (internal/child_process.js:962:16) at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5) [nginx] starting... nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1 [nginx] starting... nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/conf.d/include/resolvers.conf:1 [nginx] starting... nginx: [emerg] invalid ```
kerem commented 2026-02-26 06:32:22 +03:00
Author
Owner
Copy link

@johntdavis84 commented on GitHub (Dec 16, 2020):

I'm having this issue when trying to bring up the container with docker-compose -up, as well.

I'm less experienced with docker than others, and I'm not even sure where the /etc/nginx/conf.d/ directory is supposed to be. Is it in a container? On the host server? I looked on my Pi, and there's no conf.d folder in the /etc/nginx directory in the host filesystem.

EDIT: The local address it's complaining about is [fe80::211:32ff:fead:828f%eth0]. So it's not identical to the one above, which makes me unsure whether it's coming from inside the container or not.

<!-- gh-comment-id:745817468 --> @johntdavis84 commented on GitHub (Dec 16, 2020): I'm having this issue when trying to bring up the container with `docker-compose -up`, as well. I'm less experienced with docker than others, and I'm not even sure where the /etc/nginx/conf.d/ directory is supposed to be. Is it in a container? On the host server? I looked on my Pi, and there's no conf.d folder in the /etc/nginx directory in the host filesystem. **EDIT:** The local address it's complaining about is [fe80::211:32ff:fead:828f%eth0]. So it's not identical to the one above, which makes me unsure whether it's coming from inside the container or not.
kerem commented 2026-02-26 06:32:22 +03:00
Author
Owner
Copy link

@phrogg commented on GitHub (Apr 26, 2021):

Also experiencing the same issue since I setup the container with the network mode host because of fail2ban.

<!-- gh-comment-id:826983357 --> @phrogg commented on GitHub (Apr 26, 2021): Also experiencing the same issue since I setup the container with the network mode **host** because of fail2ban.
kerem commented 2026-02-26 06:32:22 +03:00
Author
Owner
Copy link

@JonasVgt commented on GitHub (Apr 26, 2021):

This is probably the same issue i am having at #1015

<!-- gh-comment-id:827004406 --> @JonasVgt commented on GitHub (Apr 26, 2021): This is probably the same issue i am having at #1015
kerem commented 2026-02-26 06:32:22 +03:00
Author
Owner
Copy link

@LordChunk commented on GitHub (May 28, 2021):

Not sure if this workaround is good practice, but I resolved this issue by doing the following.

  • Attach to your docker container running Nginx Proxy Manager and run ifconfig
  • Copy the Scope:Link IPv6 address
    image
  • Open /config/nginx/resolvers.conf
  • Replace the current IPv6 address in the brackets with the one you copied in step 2.
    Your file should look something like this.
    image
  • Save the file and you should be done (in my case I didn't have to restart the container).
<!-- gh-comment-id:850477619 --> @LordChunk commented on GitHub (May 28, 2021): Not sure if this **workaround** is good practice, but I resolved this issue by doing the following. - Attach to your docker container running Nginx Proxy Manager and run ``ifconfig`` - Copy the ``Scope:Link`` IPv6 address ![image](https://user-images.githubusercontent.com/23651869/120002634-5500ff00-bfd5-11eb-94eb-3abb201d9b35.png) - Open ``/config/nginx/resolvers.conf`` - Replace the current IPv6 address in the brackets with the one you copied in step 2. Your file should look something like this. ![image](https://user-images.githubusercontent.com/23651869/120002508-33077c80-bfd5-11eb-8a7f-56b2f6f9a764.png) - Save the file and you should be done (in my case I didn't have to restart the container).
kerem commented 2026-02-26 06:32:22 +03:00
Author
Owner
Copy link

@phrogg commented on GitHub (May 28, 2021):

  • /config/nginx/resolvers.conf

I can confirm this worked for me! But I had to change the path of the file. /etc/nginx/conf.d/include/resolvers.conf.

Also the file was overwritten really fast and I head to manipulate it several times, to get it to work.

<!-- gh-comment-id:850578029 --> @phrogg commented on GitHub (May 28, 2021): > * /config/nginx/resolvers.conf I can confirm this worked for me! But I had to change the path of the file. `/etc/nginx/conf.d/include/resolvers.conf`. Also the file was overwritten really fast and I head to manipulate it several times, to get it to work.
kerem commented 2026-02-26 06:32:22 +03:00
Author
Owner
Copy link

@LordChunk commented on GitHub (Jun 6, 2021):

  • /config/nginx/resolvers.conf

I can confirm this worked for me! But I had to change the path of the file. /etc/nginx/conf.d/include/resolvers.conf.

Also the file was overwritten really fast and I head to manipulate it several times, to get it to work.

Oh, I didn't have that issue. I'm running it on Docker, so the behaviour might be somewhat different to your situation.

<!-- gh-comment-id:855384119 --> @LordChunk commented on GitHub (Jun 6, 2021): > > * /config/nginx/resolvers.conf > > I can confirm this worked for me! But I had to change the path of the file. `/etc/nginx/conf.d/include/resolvers.conf`. > > Also the file was overwritten really fast and I head to manipulate it several times, to get it to work. Oh, I didn't have that issue. I'm running it on Docker, so the behaviour might be somewhat different to your situation.
kerem commented 2026-02-26 06:32:22 +03:00
Author
Owner
Copy link

@phrogg commented on GitHub (Jun 6, 2021):

  • /config/nginx/resolvers.conf

I can confirm this worked for me! But I had to change the path of the file. /etc/nginx/conf.d/include/resolvers.conf.
Also the file was overwritten really fast and I head to manipulate it several times, to get it to work.

Oh, I didn't have that issue. I'm running it on Docker, so the behaviour might be somewhat different to your situation.

Yeah I'm running it on docker as well.

<!-- gh-comment-id:855384374 --> @phrogg commented on GitHub (Jun 6, 2021): > > > * /config/nginx/resolvers.conf > > > > > > I can confirm this worked for me! But I had to change the path of the file. `/etc/nginx/conf.d/include/resolvers.conf`. > > Also the file was overwritten really fast and I head to manipulate it several times, to get it to work. > > Oh, I didn't have that issue. I'm running it on Docker, so the behaviour might be somewhat different to your situation. Yeah I'm running it on docker as well.
kerem commented 2026-02-26 06:32:22 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Mar 29, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2026458499 --> @github-actions[bot] commented on GitHub (Mar 29, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 06:32:22 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (May 9, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2864890851 --> @github-actions[bot] commented on GitHub (May 9, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear labels   
awaiting feedback

   
bug

   
cannot reproduce

   
dns provider request

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
need more info

   
no certbot plugin available

   
product-support

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#333
No description provided.