mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #873] Access list didn't work #740
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#740
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dartymath on GitHub (Feb 7, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/873
Checklist
jc21/nginx-proxy-manager:latestdocker image?Yes is the last docker jc21/nginx-proxy-manager:latest 2.7.3
Issue on Access List more precisely the client ip address is not good : always 172.18.0.1 (gateway on docker)
Describe the bug
Version 2.7.3 lastest ! when using access list -> always 403 Forbidden reach !
on the log file of the concern proxy host i can find that the ip client address register is in fact the gateway of the container 172.18.0.1 and not the real address of the client -> normal it doesn't work.
This Client address is obtain on both for Internal client requery of external with 4G mobile phone
I try different advanced option report on other issues "Nginx PM not recognizing my actual IP I am connecting with, but rather a Cloudflare IP. #811" and "IP address - Docker #112" without success
Can you help me please
To Reproduce
Steps to reproduce the behavior:
[07/Feb/2021:16:11:33 +0000] - - 403 - GET https morse.xx-xx.fr "/" [Client 172.18.0.1] [Length 182] [Gzip 3.23] [Sent-to 192.168.0.19] "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.146 Safari/537.36" "http://192.168.0.19:281/"
[07/Feb/2021:16:11:33 +0000] - - 403 - GET https morse.xx-xx.fr "/favicon.ico" [Client 172.18.0.1] [Length 182] [Gzip 3.23] [Sent-to 192.168.0.19] "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.146 Safari/537.36" "https://morse.xx-xx.fr/"
[07/Feb/2021:16:12:51 +0000] - - 403 - GET https morse.xx-xx.fr "/" [Client 172.18.0.1] [Length 182] [Gzip 3.23] [Sent-to 192.168.0.19] "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.146 Safari/537.36" "http://192.168.0.19:281/"
[07/Feb/2021:16:12:51 +0000] - - 403 - GET https morse.xx-xx.fr "/favicon.ico" [Client 172.18.0.1] [Length 182] [Gzip 3.23] [Sent-to 192.168.0.19] "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.146 Safari/537.36" "https://morse.xx-xx.fr/"
[07/Feb/2021:16:15:26 +0000] - - 403 - GET https morse.xx-xx.fr "/" [Client 172.18.0.1] [Length 182] [Gzip 3.23] [Sent-to 192.168.0.19] "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.146 Safari/537.36" "http://192.168.0.19:281/"
[07/Feb/2021:16:15:26 +0000] - - 403 - GET https morse.xx-xx.fr "/favicon.ico" [Client 172.18.0.1] [Length 182] [Gzip 3.23] [Sent-to 192.168.0.19] "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.146 Safari/537.36" "https://morse.xx-xx.fr/"
[07/Feb/2021:16:17:30 +0000] - - 403 - GET https morse.xx-xx.fr "/" [Client 172.18.0.1] [Length 171] [Gzip 3.23] [Sent-to 192.168.0.19] "Mozilla/5.0 (Linux; Android 10; SM-G973F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.152 Mobile Safari/537.36" "-"
[07/Feb/2021:16:17:30 +0000] - - 403 - GET https morse.xx-xx.fr "/favicon.ico" [Client 172.18.0.1] [Length 171] [Gzip 3.23] [Sent-to 192.168.0.19] "Mozilla/5.0 (Linux; Android 10; SM-G973F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.152 Mobile Safari/537.36" "https://morse.xx-xx.fr/"
[07/Feb/2021:16:17:34 +0000] - - 403 - GET https morse.xx-xx.fr "/" [Client 172.18.0.1] [Length 171] [Gzip 3.23] [Sent-to 192.168.0.19] "Mozilla/5.0 (Linux; Android 10; SM-G973F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.152 Mobile Safari/537.36" "-"
[07/Feb/2021:16:17:35 +0000] - - 403 - GET https morse.xx-xx.fr "/favicon.ico" [Client 172.18.0.1] [Length 171] [Gzip 3.23] [Sent-to 192.168.0.19] "Mozilla/5.0 (Linux; Android 10; SM-G973F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.152 Mobile Safari/537.36" "https://morse.xx-xx.fr/"
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots



If applicable, add screenshots to help explain your problem.
Operating System
Synolody DSM
Additional context
Add any other context about the problem here, docker version, browser version if applicable to the problem. Too much info is better than too little.
@dartymath commented on GitHub (Feb 7, 2021):
Just to precise, I have the same issue when I install Nginx Proxy Manager as addon in Home Assistant or with another docker jlesage/nginx-proxy-manager.
The issue seems to come froml the version 2.7.3
@christofkac commented on GitHub (Dec 30, 2021):
Hi,
I have a similar problem:
I want to access a Grafana dashboard which loads data from an influxdb.
Strangely, some data is read correctly and for some data I get the error 403 like in the post above.
Here some examples:
After having had a deeper look I found one difference between the successful and the unsuccessful posts:
Successful posts contain "[Gzip -] "
Unsuccessful posts carry "[Gzip 3.23]", exactly as for the user creating this issue.
Is this a bug in nginx itself?
Bye
Christof
@christofkac commented on GitHub (Dec 30, 2021):
Hi,
I played around with the rest API and found out, that the option "block common exploits" was the issue. I guess because the requests which was rejected contained the string "javascript".
Disabling this option made it work.
Hope that helps somebody else.
Bye
Christof
@chaptergy commented on GitHub (Dec 30, 2021):
The solution to the original issue is here: https://github.com/jc21/nginx-proxy-manager/issues/1105#issuecomment-950384265