nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn also related

what i have observed is that it doesn't connect at first at all, and when i click on the link, it connects and shows like this, looks like it received a tiny little message and quit listening, but no error

though the console prints this

so i'm guessing my relay is disconnecting? it doesn't even get to the first stage of running the http handler when this happens, i see nothing in my logs saying connected, and i don't see it with netstat either, like the connection is being reset for some other reason

note that it does work with the production version of nostrudel, which is about a month old, so this is a new change somewhere, and i've tried switching from gorilla websocket to fasthttp websocket library (was originally the latter) and no beans there either... the connection negotiation fail seems to be at TCP level by the looks of it

Reply to this note

Please Login to reply.

Discussion

i'm just gonna check if it isn't because of new code imported by an update to the websocket libraries

Seems to be working fine for me. In firefox I do see two requests to the relay, but maybe Firefox splits out the http and ws upgrade? Anyway, I'm sending stuff successfully.

ok, that's encouraging, thanks for poking at it