Oddbean new post about | logout
▲ ▼
Vitor Pamplona | 14 days ago (raw) | root | parent | reply | flag 
 Wait, does it get to 95% and you don't see any lightning payment on coinos at all? Then, there might be something wrong with the request itself. Or maybe a budget limitation that was setup on coinos?
▲ ▼
SLCW | 14 days ago (raw) | root | parent | reply | flag 
 Yes that's correct. The wheel gets to about 95% complete (about the 11 o'clock position) and it just hangs. Not indication of any communication with Coinos.io, no corresponding zap entries in my inbox relays. I don't think it's a budget issue with coinos.io because I can immediately paste the same NWC connect string into Primal and it zaps just fine.
▲ ▼
SLCW | 14 days ago (raw) | root | parent | reply | flag 
 This is why I'm curious if this is me problem, or if it's a wider systemic issue.
▲ ▼
Vitor Pamplona | 14 days ago (raw) | root | parent | reply | flag 
 This other user seemed to have fixed it. But his issue was different. The zap wasn't arriving because of the amount of inbox relays and limits of coinos relay lists. 

nostr:nevent1qqsz3q7ja09thcnq0s56hk22dgrg6hlqs00wegveng6kvf8alr89v7gppemhxue69uhkummn9ekx7mp0qgs8efvwljfdwa0qynp7n9dhqacf3llucdqtm9ge8kjv0dt40yw586grqsqqqqqp09f6fv
▲ ▼
SLCW | 14 days ago (raw) | root | parent | reply | flag 
 Yeah, that's different from me because I only have 3 inbox relays defined; nostr.land, relays.diggoo.com, and my personal inbox/outbox relay from relay.tools. And I just added relay.coinos.io to see if that made a difference.
▲ ▼
SLCW | 14 days ago (raw) | root | parent | reply | flag 
 So it looks like the problem was on my end after all. Turns out my system DNS blocker was interfering with the zaps. I exempted Amethyst from the DNS blocker and it's now working fine.