QUIC_PROTOCOL_ERROR

[umk0m1qk]

In the country of <REDACTED, but NOT China>, there appears to be some limitations on QUIC. When attempting to access njump.me, I get ERR_QUIC_PROTOCOL_ERROR. If I tunnel outside <REDACTED, but NOT China>, then all is well from the same device, same browser. Any way to configure a fallback for njump.me on TCP? I don't have any reason to believe this is targeted blocking (yet). More than likely, it is some technical limitation in local ISP infrastructure.

UPDATE: Just ran a test at quic.nginx.org from same device/browser/ISP WITHOUT tunneling outside, and the connection succeed. So, unfortunately, this does appear to be targeted blocking of njump.me.

[fiatjaf]

Interesting to learn that a country that isn't China is blocking njump.me.

I think @cxplay is running an alternative version, maybe you could try that one.

[cxplay]

It's weird, you can try using alternative instances nostr.at / nostr.com or my instance nostr.cxplay.org.

[umk0m1qk]

It gets weirder. Ran a few checks all from same ISP, device, browser as before...

nostr.at - returns same QUIC error as njump.me
nostr.com - works w/o issue
nostr.cxplay.org - works w/o issue

[fiatjaf]

Which one of these is using Cloudflare? njump.me is.

[cxplay]

nostr.at and nostr.cxplay.org are

[fiatjaf]

Then it's not Cloudflare.