Nostr Web Client

Can you help me copy the log? I'm also have some auth problems with auth.nostr1.com before, not sure it same error as you.

I've also running a free relay for nip17, you can try it too: wss://nip17.com

verbiricha 5mo ago 💬 1

i'll add that relay. here are the logs:

```

2025-08-05T10:37:49.419807Z INFO coop: Connected to bootstrap relays

2025-08-05T10:37:49.420162Z INFO coop: Connected to search relays

2025-08-05T10:37:49.491796Z INFO auto_update: Checking for updates...

2025-08-05T10:37:49.510850Z ERROR cargo_packager_updater: failed to check for updates: error sending request for url (https://coop-updater.reya.su/)

2025-08-05T10:37:49.674394Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://relay.primal.net'

2025-08-05T10:37:49.682092Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://purplepag.es'

2025-08-05T10:37:49.715597Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://nostr.wine'

2025-08-05T10:37:49.766815Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://relay.damus.io'

2025-08-05T10:37:49.831925Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://relay.nostr.band'

2025-08-05T10:37:49.930701Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://user.kindpag.es'

2025-08-05T10:37:49.984687Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://search.nos.today'

2025-08-05T10:37:55.010566Z INFO identity: Getting all user's metadata and messages...

2025-08-05T10:37:55.011009Z INFO registry: Starting to load chat rooms...

2025-08-05T10:37:55.011494Z INFO registry: Starting to load chat rooms...

2025-08-05T10:37:55.051438Z INFO coop: Subscribed to get DM relays: nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg - Relays: {RelayUrl("wss://frens.nostr1.com/"), RelayUrl("wss://filter.nostr.wine/"), RelayUrl("wss://pyramid.fiatjaf.com/"), RelayUrl("wss://auth.nostr1.com/")}

2025-08-05T10:37:55.233233Z ERROR nostr_relay_pool::relay::inner: Connection failed. url=wss://pyramid.fiatjaf.com/ error=HTTP error: 429 Too Many Requests

2025-08-05T10:37:55.463374Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://frens.nostr1.com/'

2025-08-05T10:37:55.483993Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://auth.nostr1.com/'

2025-08-05T10:37:55.648099Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://filter.nostr.wine/'

2025-08-05T10:37:55.767465Z INFO nostr_relay_pool::relay::inner: Authenticated to relay. url=wss://auth.nostr1.com/

2025-08-05T10:37:55.859871Z INFO nostr_relay_pool::relay::inner: Authenticated to relay. url=wss://filter.nostr.wine/

2025-08-05T10:37:56.010870Z ERROR nostr_relay_pool::relay::inner: Impossible to handle relay message. url=wss://auth.nostr1.com/ msg=["OK","",true,""] error=Invalid event ID

2025-08-05T10:38:05.769433Z ERROR nostr_relay_pool::relay::inner: Can't authenticate to relay. url=wss://auth.nostr1.com/ error=timeout

2025-08-05T10:38:05.875143Z ERROR nostr_relay_pool::relay::inner: Impossible to handle relay message. url=wss://auth.nostr1.com/ msg=["OK","",true,""] error=Invalid event ID

2025-08-05T10:38:06.481596Z WARN nostr_relay_pool::relay::inner: Timeout reached for subscription, auto-closing. id=15cff13bbf11cbf22942f31b262c59b9

2025-08-05T10:38:06.481596Z WARN nostr_relay_pool::relay::inner: Timeout reached for subscription, auto-closing. id=b9aaf43e46cdc61161f60997186995f1

2025-08-05T10:38:06.482136Z INFO coop: Subscribed to get DM relays: nostr:npub1sgx8tkmn2gm4s788tssy5kgx0qjw9q8efda7wmg4afuyx2smdcjq2q7wnj - Relays: {RelayUrl("wss://relay.primal.net"), RelayUrl("wss://relay.damus.io"), RelayUrl("wss://nos.lol")}

2025-08-05T10:38:06.834408Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://nos.lol'

2025-08-05T10:38:15.771578Z ERROR nostr_relay_pool::relay::inner: Can't authenticate to relay. url=wss://auth.nostr1.com/ error=timeout

2025-08-05T10:38:15.878343Z ERROR nostr_relay_pool::relay::inner: Impossible to handle relay message. url=wss://auth.nostr1.com/ msg=["OK","",true,""] error=Invalid event ID

2025-08-05T10:38:16.484516Z WARN nostr_relay_pool::relay::inner: Timeout reached for subscription, auto-closing. id=bef88b2b890ab0efe9e88924fddfe7c5

2025-08-05T10:38:16.485484Z INFO coop: Subscribed to get DM relays: nostr:npub1vp8fdcyejd4pqjyrjk9sgz68vuhq7pyvnzk8j0ehlljvwgp8n6eqsrnpsw - Relays: {RelayUrl("wss://relay.nostr.band"), RelayUrl("wss://premium.primal.net"), RelayUrl("wss://auth.nostr1.com"), RelayUrl("wss://inbox.nostr.wine"), RelayUrl("wss://nostr.wine"), RelayUrl("wss://relay.0xchat.com")}

2025-08-05T10:38:16.552538Z INFO registry: Starting to load chat rooms...

2025-08-05T10:38:16.741696Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://premium.primal.net'

2025-08-05T10:38:17.120991Z INFO nostr_relay_pool::relay::inner: Connected to 'wss://inbox.nostr.wine'

2025-08-05T10:38:17.171455Z ERROR nostr_relay_pool::relay::inner: Connection failed. url=wss://relay.0xchat.com error=HTTP error: 403 Forbidden

```

Reply to this note

Please Login to reply.

Discussion

reya 5mo ago 💬 2

I think the problem is this log:

```

2025-08-05T10:38:05.875143Z ERROR nostr_relay_pool::relay::inner: Impossible to handle relay message. url=wss://auth.nostr1.com/ msg=["OK","",true,""] error=Invalid event ID

```

rust-nostr-sdk is verifying the auth response, it required relay must response with event id like describe in nip-42, but auth.nostr1.com just respond with "", so it cause the error Invalid event ID

this issue happen with me too, but strangely if I use login with nsec, it's working fine 🥲. Anyway I will find a way to fix it.

verbiricha 5mo ago 💬 2

oh i see, cc nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h so you are aware. i'm using nsec too #yolo

reya 5mo ago

When you restart Coop, do you still see empty messages, or does it load now? If not, there is a bug somewhere, and I need to check it.

cloud fodder 5mo ago

nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445 this is strange. I am unsure how the relay would say OK without an event ID this should never happen. It could be a bug with multi-auth or something but I would need to see a dump of the websocket to debug. Typically I use wireshark for this.

hzrd149 5mo ago 💬 2

I also ran into with issue on this relay when building nip-17 support for noStrudel

Didn't end up fixing it, the auth just times out :(

reya 5mo ago 💬 1

I ended up running a free relay for DMs 😂. you can try it here: wss://nip17.com

hzrd149 5mo ago 💬 2

While I have your attention. What do you think about using NIP-40 on the gift wrap event to support messages that "disappear".

I've found that it's kind of nice to have the DM auto remove themselves after a few weeks.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

expiration tags should do this, what is that, nip-70 lol, these numbers.

reya 5mo ago

Yes, I think it is the easiest way for now. I will add support for it in Coop later.

cloud fodder 5mo ago 💬 1

well crap

cloud fodder 5mo ago 💬 2

nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr tried nostrudel with my only DM relay is auth.nostr1.com so it must be your bug. I had to tell it my nip17 relay list (of one relay by hand) and then click the "yes i want to authenticate". works fine. perhaps the problem is when you use more than one relay or something :megashrug: :sweating: 🌝

cloud fodder 5mo ago

Of course, by "works fine" I mean, the websocket does what it's supposed to do, and nostrudel downloads all the giftwraps. Then since I told it no cache, I suppose it just kind-of fails to decrypt them, even though I gave it a lot of time, the button just seems to do nothing.. Then each time I try to click around, it opens new websockets to auth.nostr1.com that also I assume are lurking asking me to auth but they don't actually ask me so those connections stall.

hzrd149 5mo ago 💬 1

Looks like its working now. I remember it having a bug at one point but that was a month ago when I was working on NIP-17 stuff

https://cdn.hzrd149.com/2a153953ccdf83cf606ff33d6538c0b27c9e9a082ea1443d5ec321479e4f087a.webp

cloud fodder 5mo ago 💬 1

oh good, good. yeah nothing has been changed in that auth code for many months (last change was multi-auth support).

hzrd149 5mo ago

Maybe it was a different relay. but I do remember running into an issue where it responded with an empty event id

Either way thanks for running that relay. it helps with my DMs