What was issue?
Discussion
good question. nostr:npub1q5sah9f3p9kl7uqdeaqskqwmg74ktxx70e0093dzh4lpzcp3t0mqzxky65 did something something and now it works.
Huh, maybe nostr:nprofile1qqsq2gwmj5csjm0lwqxu7sgtq8d502m9nr08uhhjck3t6ls3vqc4haspz4mhxue69uhk2er9dchxummnw3ezumrpdejqzyrhwden5te0dehhxarj9emkjmn9qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsxdd778 could help me...
How can I help ?🙂
Actually I did not do anything. If you have a public channel it is recommended to restart your Hub.
(But you only need public channels if you plan to receive podcast payments). Otherwise just go with private channels. Everybody can send you zaps.
Messages to support@getalby.com are usually answered quicker.
I have only one opened channel maybe that is problem, no route error...Sometimes zap go through sometimes fails.
We recommend to have at least two channels for redundancy and better connectivity in the network.
Who is your channel peer?
LnServer
That's a good channel partner. The receiving side could be not well enough connected. If you see failed payments despite the receiver has a well connected wallet, we need to look into it.
Yes, interesting thing is that when I zap myself that goes through. What I see on alby hub node section is node health is at 47%. What read on faq about it is that I have low sending or receiving capacity which is not the case here.
oh so restarting was all I had to do? That's good to know. As for public vs private nodes, that was me playing around not knowing what I'm doing 😉
He did. It's all working now 😉
Sorry I read that wrong. (more coffee)