Replying to Avatar Thorwegian 🇳🇴

(using NRCheck i mean)
78
78e47dfe... 2y ago

mostly: Can't connect to wss://nostr.jatm.link (caught exception)

a good bunch of : Info fetch timeout for wss://www.weixin.com

about 15 like : Access to fetch at 'https://nostr.easify.de/' from origin 'https://nrcheck.tigerville.no' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values '*, *', but only one is allowed. Have the server send the header with a valid value, or, if an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

and a handfull of: Failed to load resource: net::ERR_FAILED

Reply to this note

Please Login to reply.

Discussion

78
78e47dfe... 2y ago

Do I tried the client on windows aswell, and both on mobile network and wifi. I get different results when I'm not using Brave btw

78
78e47dfe... 2y ago

this is somewhat more typical using Impervious browser

78
78e47dfe... 2y ago

I guess turning off shields in Brave isnt enough

Avatar
Thorwegian 🇳🇴 2y ago

if you're getting 300 "didn't connect at all" you should also be getting 300 WebSocket errors in the console. it should be the most common error message. if your browser isn't letting you talk to remote WebSocket servers, you're going to have low visibility.