-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Stateless and TLS-ALPN-01 #4926
Comments
Please upgrade to the latest code and try again first. Maybe it's already fixed. |
I'm using the latest version and the relevant log line is already included in my issue comment. |
you can try to use Let's encrypt CA, run the command: |
@jueduizone Thanks for your reply, but I don't see how this would help me unless LE would be using 'stateless' and 'http-alpn-01' by default. Is that the case? I would like to handle both, challenge- and application-traffic, on port 443, if possible. In addition, stateless mode is a hard requirement for my usecase. |
No. |
@Neilpang Thanks for answering. Are there any plans to implement this functionality in the future and/or would you accept a PR for that? |
Hi there,
is it possible to use
stateless
mode with aTLS-ALPN-01
challenge? I tried:But it seems like
HTTP-01
is used:Am I'm doing it wrong or does
acme.sh
currently not support that scenario?The text was updated successfully, but these errors were encountered: