[GH-ISSUE #915] container behind proxy can't navigate using proxy as gateway #777

Closed
opened 2026-02-26 06:34:22 +03:00 by kerem · 9 comments
Owner

Originally created by @openaspace on GitHub (Feb 24, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/915

Hello.
I have installed proxy on the alpine linux lxc and it works correctly,
but any lxc behind the proxy within the virtual network can't get internet connection.

Any info ?

Originally created by @openaspace on GitHub (Feb 24, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/915 Hello. I have installed proxy on the alpine linux lxc and it works correctly, but any lxc behind the proxy within the virtual network can't get internet connection. Any info ?
kerem 2026-02-26 06:34:22 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@fabianohugo commented on GitHub (Feb 24, 2021):

I have the same problem. I put a VPN here in the company and when I connect to it, none of my URLs work with the virtual network..

Ticket

<!-- gh-comment-id:785232451 --> @fabianohugo commented on GitHub (Feb 24, 2021): I have the same problem. I put a VPN here in the company and when I connect to it, none of my URLs work with the virtual network.. [Ticket](https://github.com/jc21/nginx-proxy-manager/issues/894)
Author
Owner

@openaspace commented on GitHub (Feb 24, 2021):

If the proxy don't act also as gateway for the virtual network , you can't contact externals NS to find your IP domains.. in this case I think you need a local NS or don't route the wan traffic inside the VPN.

<!-- gh-comment-id:785293542 --> @openaspace commented on GitHub (Feb 24, 2021): If the proxy don't act also as gateway for the virtual network , you can't contact externals NS to find your IP domains.. in this case I think you need a local NS or don't route the wan traffic inside the VPN.
Author
Owner

@fabianohugo commented on GitHub (Feb 24, 2021):

But in this case, wouldn't it be just releasing the virtual network inside nginx? or in the case iptables of the docker then?

<!-- gh-comment-id:785319178 --> @fabianohugo commented on GitHub (Feb 24, 2021): But in this case, wouldn't it be just releasing the virtual network inside nginx? or in the case iptables of the docker then?
Author
Owner

@openaspace commented on GitHub (Feb 24, 2021):

I don't know your conf and I use proxmox containers

<!-- gh-comment-id:785324087 --> @openaspace commented on GitHub (Feb 24, 2021): I don't know your conf and I use proxmox containers
Author
Owner

@fabianohugo commented on GitHub (Feb 24, 2021):

I'm using the Nginx Proxy Manager project, on a docker installed on Centos

<!-- gh-comment-id:785336798 --> @fabianohugo commented on GitHub (Feb 24, 2021): I'm using the Nginx Proxy Manager project, on a docker installed on Centos
Author
Owner

@fabianohugo commented on GitHub (Feb 24, 2021):

I tried to put the upstream not hand, but it didn't work.
ins custom files
upstream www.site.com {
server 172.1.7.2:3001 fail_timeout=60;
}

<!-- gh-comment-id:785341523 --> @fabianohugo commented on GitHub (Feb 24, 2021): I tried to put the upstream not hand, but it didn't work. ins custom files upstream www.site.com { server 172.1.7.2:3001 fail_timeout=60; }
Author
Owner

@fabianohugo commented on GitHub (Feb 24, 2021):

And in the app I don't know how to put upstream to work. On the web platform

<!-- gh-comment-id:785342351 --> @fabianohugo commented on GitHub (Feb 24, 2021): And in the app I don't know how to put upstream to work. On the web platform
Author
Owner

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

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

<!-- gh-comment-id:2002735448 --> @github-actions[bot] commented on GitHub (Mar 18, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Apr 29, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2837247048 --> @github-actions[bot] commented on GitHub (Apr 29, 2025): Issue was closed due to inactivity.
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#777
No description provided.