3/21/2024 0 Comments Proxy vs reverse proxy nginx![]() Why not use Traefik to direct traffic?īecause it’s really hard and we couldn’t figure it out is why. We were already using Traefik as an ingress proxy on another Docker stack, so we wondered if we could just switch everything over to Traefik here as well, since the only work the ext01 proxy was doing was, well, directly traffic. I’ll explain what we tried and why we gave up first, but if you don’t care, just skip ahead to the part about how we got NGINX to do what we wanted. We tried using Traefik and HAProxy, but ultimately gave up and used NGINX. But that meant the docker web stack would need to use different ports to port 80 and 443 so that the existing traffic via the proxy kept flowing.Īnd it also meant that we’d need the NGINX proxy to be able to tell the difference between existing traffic for playnice and the new traffic for our new sites.īut how? The eigenlab reverse proxy lab network showing the three kinds of traffic we need to proxy and route. When we first started this project, we had an existing project ( ) sitting behind an NGINX reverse-proxy on ext01, so we needed to keep that working while we added the docker web stack to ext01. This post continues on from the first post in this series on setting up a reverse proxy lab.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |