mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #894] Access to the internal website after connecting to a vpn (wireguard) #759
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#759
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 @fabianohugo on GitHub (Feb 15, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/894
Hi! I have the following environment. I set up Nginx Proxy Manager as my main request receiver for my sites. So I had to set up a vpn for people to stay in the home office. Without the VPN, the sites are functioning normally, but when I connect to the VPN my site gives an ERR_CONNECTION_REFUSED error. I'm not using upstream (I don't know if it's necessary). Can you help me? Where I release it. It is very likely that I have to release the VPN IP or the Public IP on Nginx.?

@fabianohugo commented on GitHub (Feb 16, 2021):
Updating the post: I checked the upstream problem in the log.
2021/02/15 14:30:17 [error] 27318 # 27318: * 504133 connect () failed (111: Connection refused) while connecting to upstream, client: 189.90.XXX.YYY, server: wgx.sps.ce. gov.br, request: "GET /favicon.ico HTTP / 2.0", upstream: "https: //172.19.AAA.BBB: 443 / favicon.ico", host: "wgx.sps.ce.gov.br" , referrer: "https://wgx.sps.ce.gov.br/"
I haven't seen where I can fix this problem.
Can you help me?
@github-actions[bot] commented on GitHub (Mar 19, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 30, 2025):
Issue was closed due to inactivity.