Thread

🛡️
Do you get the same error with older versions of ngit? The last time rust-nostr changed the connection logic was v0.39 according to the change log and its on v0.44 now. I only noticed this as an intermittent problem in the last 2 weeks. It effected connecting to other relays but never all the repo relays at once. This makes me think its a rust-nostr/ngit ssue rather than a problem at the relay end. I bumped master to rust-nostr v0.44.1 yesterday.

Replies (2)

🛡️
I was getting it yesterday with my old ngit version (like from 2 or more months before that I had been using without any issues). I only updated after I started getting the bug. I was trying with a VPN, but I also tried without the VPN, the result was always the same. Sometimes (rarely) I get a green check on one of the two grasp servers: ~> git push nostr: fetching... ✔ wss://gitnostr.com no new events ✔ wss://relay.damus.io no new events ✘ wss://relay.ngit.dev timeout after 7s timeout ✔ wss://nos.lol no new events ✔ wss://pyramid.fiatjaf.com/ new events: 1 user profile ✔ wss://relay.westernbtc.com/ no new events ✔ wss://relay.nostr.band no new events nostr updates: 1 user profile fetching relay.ngit.dev/npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6/nostrlib.git ref list over https (unauthenticated)... list: connecting... list: failed: failed to connect to relay.ngit.dev: Operation timed out; class=Net (12) fetching gitnostr.com/npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6/nostrlib.git ref list over https (unauthenticated)... list: connecting... list: failed: failed to connect to gitnostr.com: Operation timed out; class=Net (12) Everything up-to-date But the push fails anyway.