Closed SuperJakish closed 5 years ago
I'm not familiar with the apps you are referencing, and I don't really have time to look too closely at the config file you've pasted, but at a glance, it looks like its doing a lot more than simply proxying.
Usually the configurations you add to this image would only proxy back to other containers. Also make sure to refer to those containers using the names of those containers. Docker assigns them RFC1918 IP addresses which you can reference with the name of the container. 127.0.0.1 won't work.
The "proxy.conf" in this repo is a good approximation of the config you need for each vhost.
Also know that there are others who have published let's encrypt certificate management proxies which may be a better choice for you if you have multiple vhosts. It can be done with this container, but it's not as elegant as it could be.
Thanks for the insite. I'll poke around some more and see what I can find.
Hey there! I was able to get this working with docker-compose on my ubuntu system to the point where I could reach my landing page from outside my network with SSL enabled. Super cool! I'm running into an issue with adding another config file and setting up a reverse proxy for the services running in other docker containers. I can navigate all of the other containers on my local network, so I know they are running, but I can't see them from outside the network.
Here is a grab from my docker-compose.yml file:
If I comment out the volume call for my custom config file, I land on the organizr page. Whenever I try to add proxy calls to my other containers and include the volume call, the whole things breaks and I can't see the organizr landing page.
Here is my ombi.conf file for reference:
Do you have any thoughts you would be willing to share with me? Thank you kindly!