Replies: 1 comment 1 reply
-
The 301 is not redirecting to itself but redirecting to https. So http>https If you don’t want the port 80 listener (where this 301 redirect is) read this: Especially: |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Order of operations.
I first create the NGINX container:
HTTP
If I create my service container immediately after this, using this commend:
with no ACME container set up, the initial routes for only HTTP look like this:
This is absolutely fantastic, I can connect to it using CURL or whatever other random client I have.
HTTPS
If, instead of immediately starting my service, I use the following command to start an ACME companion container:
docker run --detach \ --name nginx-proxy-acme \ --volumes-from nginx-proxy \ --volume /var/run/docker.sock:/var/run/docker.sock:ro \ --volume acme:/etc/acme.sh \ --env "DEFAULT_EMAIL=x@x.x" \ nginxproxy/acme-companion
Then those previously fine routes get replaced with the following:
So the default HTTP route gets 301 redirected to itself for some reason.
I'm using Cloudflare HTTPS proxying for now to keep some semblance of security, but I think it would be nice to have a proper HTTPS reverse proxy inside the docker network. Any help would be much appreciated!
Beta Was this translation helpful? Give feedback.
All reactions