Open JonasVgt opened 3 years ago
Thanks for the detailed report. I don't see why we can't include that second address in the resolvers. Shouldn't be too hard to fix the regex.
Issue is now considered stale. If you want to keep it open, please comment :+1:
same error
nginx: [emerg] invalid IPv6 address in resolver "[fe80::46d9:e7ff:fe95:e3db%br0]" in /etc/nginx/nginx.conf:13
I have made a Comment on a different Bug Report #149 but noticed later, that my problem was different to the one described there. That is why I made this separate Bug report.
The Problem
I am running this Docker Image on my Rapsberry Pi Home server. When I try to start the Container, it is marked as 'unhealthy', the web-interface will not start and the following error is repeatedly being logged:
Cause
When the Container is beeing started it will copy
/etc/resolv.conf
from the host machine (outside of the container) into the Container to the same location. The Content of that file will then be converted by the script located atnginx-proxy-manager/docker/rootfs/etc/services.d/nginx/run
of this repository in the following line:The output will then be written into
/etc/nginx/conf.d/include/resolvers.conf
. This file is read by nginx which will throw the error./etc/resolv.conf:
/etc/nginx/conf.d/include/resolvers.conf:
resolver 127.0.0.11 [fd00::3a10:d5ff:fe77:c05d] [fe80::abd:43ff:feca:7350%2] ;
Note:
fd00::3a10:d5ff:fe77:c05d
is the IP of the Router which is connected to the Internet and directly to my Server via ethernet.fe80::abd:43ff:feca:7350
is the IP of a second Router which is only responsible for the WLAN in my NetworkThe Error emerges, because one of the IPs is ending with the zone index
%2
.How to reproduce
Unfortunately I don't have any knowledge in this area and can't give an explanation on how to reproduce this behavior other than adding the IP address with zone index manually to the resolver of the host-machine. As stated before I have two Routers in my Network which might be the root cause of the Problem.
The Fix
A simple fix would be to edit the line which converts
/etc/resolv.conf
to/etc/nginx/conf.d/include/resolvers.conf
so, that it will remove the zone index or the entire scoped IP. Unfortunately I am unable to find if nginx should handle these scoped IPs or if these IPs should even exist in/etc/resolv.conf
. So this may fix a behavior which shouldn't even exist.Setup
Device: Raspberry Pi 4B Operating System: Raspbian GNU/Linux 10 (buster) Docker:
Container: jc21/nginx-proxy-manager:latest
Thank you for the Help!