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
Need assistance in private beta... #34
Comments
Is there an active proxy listening on port 80 which forwards traffic to the opt port 10443 you told lego to bind to? LE will try to access your server on port 80 for HTTP-01. |
damn thank you. I hoped I would be able to use a different port than either 80/443. It sucks to disable the nginx to update the certificates. But it works now, awesome =) |
You don't have to disable nginx. That's what the optPort is for. You could just add a temporary proxy directive to the nginx config to pass all traffic on the path /.well-known/acme/ to port 10443. :) |
let me try this. Thanks for the support! :-) |
its also hard to find that workaround in the first place. You probably have to read the whole spec get which folder to proxy. |
I agree. I should probably improve the documentation on what optPort is for. |
Thanks for the awesome project btw. |
My pleasure :) |
Just for the record, that's the nginx proxy i used:
Thanks again :D |
Hi sorry if this is more of a stupid error by me, but I can't get lego to work on my server.
Running letsencryt-auto works and creates certificates:
/opt/letsencrypt/letsencrypt-auto --agree-dev-preview --server https://acme-v01.api.letsencrypt.org/directory auth -d sub.mydomain.com--standalone
Running lego:
gets me:
Can you help me out here? I even tried the
add-tls-sni-challenge
branch, but with the same results.The text was updated successfully, but these errors were encountered: