-
Notifications
You must be signed in to change notification settings - Fork 367
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
HTTP3 - QUIC connection could not be established #466
Comments
I don't know QUIC and the RFCs are too long for me to delve into right now, but it does not look like QUIC is simply "TLS over UDP", so the TLS probe would not work. That said, if you're not share UDP 443 with another protocol, why not simply have your Web server listen to UDP 443, while sslh listens to TCP 443? |
Good idea ! EDIT: |
I'll do that myself, but if you ever do come up with a specific probe, that would be better |
you do that yourself ? |
Lol appologies, it was late when I saw this and responded. I mean to say yrutschle's solution does indeed work for the time being, but of course means I cant leverage udp for coturn or something else as well. |
Hello
I have an issu with sslh.
With this settings:
Using https://http3check.net/
I got
QUIC connection could not be established
Thanks for help
The text was updated successfully, but these errors were encountered: