Single IP with multiple ports but only 1 is working #4750
-
|
I have several docker containers setup for different applications all running on the same server as NPM. I setup a wildcard SSL certificate for my domain. I created my first proxy host, pointed it to the server ip and the specific port for that application, used my wildcard cert and it is working perfectly! I added an additional proxy host, pointed it to the server and the unique port for the 2nd application, used my wildcard cert again and get nowhere. Gateway timeout error code 504. I gave the npm docker container access to the other container's networks and tested from the npm container that it can communicate with the other services by service name. Am I trying to do something not supported? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Sometimes I just need to think it out loud. When I tested communication from npm docker container to the other containers I could ping by service name. So I changed my proxy hosts in NPM to hostname (service name) instead of the shared server IP and kept the ports according to the service and BINGO! Everything is resolving now! Hopefully this helps the next person. |
Beta Was this translation helpful? Give feedback.
Sometimes I just need to think it out loud.
When I tested communication from npm docker container to the other containers I could ping by service name.
So I changed my proxy hosts in NPM to hostname (service name) instead of the shared server IP and kept the ports according to the service and BINGO!
Everything is resolving now!
Hopefully this helps the next person.