Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doubling up on encryption? #2

Open
steve-taylor opened this issue Mar 11, 2018 · 0 comments
Open

Doubling up on encryption? #2

steve-taylor opened this issue Mar 11, 2018 · 0 comments

Comments

@steve-taylor
Copy link

steve-taylor commented Mar 11, 2018

Why do registry's REGISTRY_HTTP_TLS_CERTIFICATE and REGISTRY_HTTP_TLS_KEY environment variables need to be set when lets-nginx is already placing a TLS layer in front of registry? Can't registry just accept plain HTTP requests over port 5000? It would stop registry from restarting 50 times because it can't find the certs until lets-nginx finishes doing its thing with letsencrypt.

Also, UPSTREAM is set to registry:80, but registry listens on port 5000.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant