mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #1736] How to install additonal NICs (and its routing rules due to "default gateway" AFTER installing proxy manager with docker? #1291
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#1291
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 @jayjupdhig on GitHub (Jan 7, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1736
1.) When i add them in /etc/network/interfaces BEFORE installing docker, it works
2.) When i add them in /etc/network/interfaces AFTER installing docker , it does not work: https://github.com/jc21/nginx-proxy-manager/issues/1734
Now i have that proof for that fact - before set up a complete new proxy vm it was just a theory...
SO: What to to when i want to add a 4rd or 5th NIC AFTER isntalling proxy manager...?
Because of proxy manager (i think because its "special" virtual NICs, bridge and so on) it makes issues: https://github.com/jc21/nginx-proxy-manager/issues/1734
@jayjupdhig commented on GitHub (Jan 7, 2022):
Maybe it's better to use an own VM for each [new] IP address / network connection to bypasss / avoid problems like that!?
@jayjupdhig commented on GitHub (Jan 10, 2022):
No anwser? The problem seems proxy manager-related to me (because of it's virtual adapters: bridge and so on!!), so NOT debian re-related. When i set up a fresh Debian [11] installation, or adding the additional adapters (eth1, eth2, ethX) BEFORE installing the proxy manager docker container, then IT WORKS!!
Otherwise, when i install them (eth1, eth2, ethX) AFTER INSTALLING proxy manager docker container, it does not work.
So: Why? Thank you very much for your feedback...
With kind regards, Jan
@jayjupdhig commented on GitHub (Jan 11, 2022):
Maybe an adequate workaround (in your opinion?) is to install each time a new VM of proxy manager if we have a new IP / network connection?
So: Number of ingoing connection IP is EQUIVALENT to the number of reverse proxy VMs...?
Or something like that...? Maybe suboptimal, but a possible to to bypass the problem i already described well!!
@chaptergy commented on GitHub (Jan 11, 2022):
As I have told you before, please stop spamming this issue tracker, this is not your personal tech support, and such behavior will not be tolerated here. No one owes you support, everyone is doing this in their spare time, and you are not paying for a product or a service. Furthermore most of your comments don't even sound friendly in tone, but rather angry and entitled. Commenting very frequently makes it seem even worse if you do not have anything useful to provide, like just cross-linking your issues.
You are obviously describing something you are experiencing with docker. This issue tracker is for Nginx Proxy Manager only. It does run in a docker container, however docker is a totally separate thing from npm. We do not provide support on how you can set up your docker environment for your super specific use-cases. You would have to research that yourself or find a community which is meant to help each other with docker issues. This is not the place.