NPM does not route to Wordpress Site #3743
Replies: 2 comments
-
Exact same issue here, Spent 2 days now trying to solve it. Various suggestions online re making new bridge network and shoving all containers in it, and then instead of specifying the IP addr, specify the wordpress container name. None of said suggestions work. I get the feeling that using this proxy manager to access other containers on the same host is simply not supported |
Beta Was this translation helpful? Give feedback.
-
Put the wordpress container on the same network as NPM and use the container name as the 'forward hostname' and 80 as the port. Docker resolves contanernames automatically within a network to the internal ips and communicates via the internal ports. |
Beta Was this translation helpful? Give feedback.
-
Hi all,
I have a Proxmox server running on which one instance contains an NPM in Docker. Another instance contains Wordpress in a Docker container.
There are already several domains that reach out to me on different services.
However, I have the problem that I cannot reach my Wordpress instance externally.
Internally it works. when i open http://192.168.1.230:8080
the domain kunst.datenreich.eu points to my NPM. This is configured as follows:
If I call the Ip internally, the website call works.
When I call kunst.datenreich.eu the url is exchanged as follows: https://kunst.datenreich.eu:8080 and the following site is displayed:
Does anyone here know what else I can do to make the website accessible?
unfortunately i have only found a few posts so far and no solution to my problem
Beta Was this translation helpful? Give feedback.
All reactions