NGINX proxy manager just works in lxc locally - not with other lxc

M

macaroni9431

New Member
Jan 30, 2025
4
0
1
Hi guys

I've been dealing with this problem for almost 2 weeks now and I can't find a solution to my problem. My general research was unfortunately unsuccessful, which leads me to believe that the solution is something trivial.

I have set up a LXC container with Docker and Nginx Proxy Manager. Other containers within this LXC container can be handled properly via Nginx.

The problem: I cannot trade any other containers or VMs with this proxy manager.

I suspect that I am still missing some setting in my proxmox environment. Does anyone have an idea for me in which direction I have to move in terms of a solution?

Thanks!!
 
Last edited:
Hey,

I don't think Docker allows its containers to reach the host network by default. Can the LXC itself reach other VMs/LXCs?
 
  • Like
Reactions: macaroni9431
Hannes Laimer said:
Hey,

I don't think Docker allows its containers to reach the host network by default. Can the LXC itself reach other VMs/LXCs?
Click to expand...
Hi Hannes

Thanks for your feedback. Yes, I successfully ping other LXC with this LXC. I have already studied 20 different installation instructions and have not found a clue to my problem in any of them. Everywhere it says: install and it works.

At the moment it looks like I have to install Nginx on every LXC container. That makes no sense to me at all.

Greetings
Macaroni
 
If the LXC can reach everything you want to reach, then this is docker not allowing communication. Either consider installing NPM on the LXC container, and not within docker, or change docker to use host[1] network mode.

[1] https://docs.docker.com/engine/network/drivers/host/
 
  • Like
Reactions: macaroni9431
Hannes Laimer said:
If the LXC can reach everything you want to reach, then this is docker not allowing communication. Either consider installing NPM on the LXC container, and not within docker, or change docker to use host[1] network mode.

[1] https://docs.docker.com/engine/network/drivers/host/
Click to expand...
Hi Hannes

I have just recreated the LXC plus NPM in Docker. In network mode host. NPM ONLY gives me a valid certificate for NPM itself. For all other LXC s I always get the message: Connection Refused. What I have noticed, however, is that an LXC container displayed a valid certificate in the browser for about 10 seconds. After that it was gone again. I'm beginning to think that Docker itself is blocking again. The PVE node itself and LXC firewall are disabled. I am at my wit's end...
 
Not sure if this helps, but for some reason after I made changes to the IP of my network (i.e. 192.168.x.0) and reconfigured everything (DNS), npm(lxc) was not able to redirect me to the other lxc containers via hostname (throws 502). I also have VMs that npm has no problem with, but for these I have always set npm to call them via IP. I checked via the console to see if I can ping the hosts from the npm lxc, seems they can be reached - so I have no idea what's going on.

I noticed that a new instance of npm (lxc) would resolve this issue, but I don't know why.

I think it happened again when I resassigned some IPs (including DNS). I wasn't expecting any complications so I wasn't really paying attention.

It is annoying to redo my npm, but at least I have a workable solution.
 
Last edited:
You must log in or register to reply here.
Top Bottom
Back