-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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 connect failed: Resource temporarily unavailable (with ngtcp2) #6864
Comments
@tatsuhiro-t any chance you can throw a quick eye on this? It looks like one of our more recent adjustments to the changing ngtcp2 APIs broke functionality and you might have a chance to spot that much faster than anyone else... |
There are couple of issues, some are client side, others are, well, version negotiation failure. Curl uses ALPN h3 Lines 354 to 355 in 0409c12
and at the same time it uses version 0xff00001d Lines 816 to 818 in 0409c12
In my opinion, we should use version 0x00000001 for ALPN h3. If we make this change, it can get from ngtcp2 server, but it fails in curl (56), which is probably another issue. If we change version to 0x00000001, it still fails with cloudflare-quc.com because it does not support QUIC v1 yet. |
This is ngtcp2 server bug. |
@bagder , @tatsuhiro-t |
Works for me: $ ./src/curl -V |
Your situation is with OpenSSL/1.1.1g? I built ngtcp2 with gnutls.
|
It looks like boringssl backed server does not like ClientHello generated by GnuTLS. It is hard for me to debug this because it is TLS internal stuff. |
"Resource temporarily unavailable" still happens to me with GnuTLS build from GitLab as of GnuTLS commit a6a45ad0 |
Comments on closed issues mostly get lost/ignored. I filed a new issue for this issue for the gnutls flavor. |
curl version: 7.76.1-DEV (commit: 3be5ebf)
But the old version works.
The text was updated successfully, but these errors were encountered: