3 Replies to “The Simplest Reverse Proxy Server for ASP.NET Core Using Docker”

  1. Hi,
    What is missing in your page… Obviously, I need to somehow tell it what my site name is for LetsEncrypt to work, I think there are other configuration things needed? (Do I need to add DNS entries for Lets Encrypt or something? It has been a LONG time since I setup one.

    How does adding a few vars to the image make it work? Do I need to use your image for the MVC app? I already have an app, can I change the base image and have it work?

  2. Bonus also says it can be used for multiple sites… so, how does that work? Do I just fire up additional images and it works? Just set the environment vars? Do both of the environment vars have the same value? (as they do in your example)? If so, why do you have two?

  3. And lastly… If I use that docker-compose.yml file, it specifies the docker image as yours, but obviously, I need that to be my image… do I have to change my DockerFile to build differently? Or can I just replace your image with my image in the docker-compose.yml file?

    Seems like you need several pages more information to get someone who hasn’t done this to be able to follow it and get it working.

    Oh, also, a note on how it works would be wonderful! I’m pretty sure the proxy issues stuff to the lets encrypt (I presume someone has to have a DNS Entry pointing at the Proxy’s ports for https in order to work.. and I presume it picks off the host name, somehow passes that to Lets Encrypt, and that does some magic to generate a cert that it writes back to the Proxy and then the proxy will use that for later requests… and it then remembers that host name and every 12 hours checks to make sure it isn’t expired and renews it (per LetsEncrypt’s recommendations)?

Leave a Reply