I talked with a smarter person I no longer think it's the OS. I think it's either our internet router or our internet service provider
the smarter person reminded me that dns lookups stop working on all of our work devices periodically and we usually fix it by restarting our router
the problem is usually discovered when someone tries to do npm install <package> on their laptop and npm just hangs, eventually telling us it can't resolve the dns name for registry.npmjs.com
the smarter person suspects it has something to do with the router trying to route over ipv6 but being busted somehow (or maybe our internet service provider is the one who's busted)
restarting the router fixes it and we've just been doing that so now I'm thinking it was maybe a poor decision to self host on a server that's connected to a router that frequently stops knowing how to map domain names to ip addresses
You can try manually adding an entry to the /etc/hosts file. I know, this will break in the long term because it's akin to just using the IP directly, but it will at least allow us to test it for now :)
Also I managed to fetch the lnurl data and now I get a different error: invalid amount. The range is apparently 4187 to 9007199254740 sats. And I'm trying with 5K, 10K and 15K sats, all with the same results.
reply
You can try manually adding an entry to the /etc/hosts file
Good idea, I just did that
I managed to fetch the lnurl data and now I get a different error: invalid amount
What wallet are you using? Your lnurl works fine in lnbits and phoenix for me
reply
I tried to pay with breez
reply
hmm breez isn't available for my phone so I can't test it, I'm sorry that it isn't working for you!
reply
Ok I tried paying with lnbits as suggested and indeed it apparently worked. But when trying to claim with an invoice generated by LND I get:
status: nice try, asking me to pay you when the invoice that pays me is about to expire
This is funny, but wrong I think, because the payment only expires in ~800 minutes.
reply
Can you paste your invoice here? I wonder if its expiration time is longer than the expiry on the invoice that pays me. My server might be worried that you might wait for me to send you the money but not give me the preimage until my invoice expires, at which point I can no longer settle the one that pays me. It protects me from that by requiring that any invoice passed to me must have a shorter expiration time than what's leftover of the one that pays me. I can check if that's what happened if you paste the invoice here.
reply
Sure, here it is:
lnbc33460n1pjw4tnhpp5aujpg5lwf5pg57thzf3u2xd3s23qhgevnj9adxv8el7su5c06yuqdqqcqzzsxqyz5vqsp5a5l58jawk3dwx3dcarvk4z90ann4gq26a97xskw6w04z0zwck39s9qyyssqlfe42yrluuwrsq8r3gmj7qzhh3jt3d2n0qzj0ga43ss0l0pcfwt4z59r86c887299yssae675ktv86k4p533pk4pmsdjdsl6098xzmgp2qve98
reply
Well I guess that was the problem, the expiration time on that invoice is 24 hours. And for what I see from your other reply the invoice your server is generating is good for 100 blocks, or ~16.6 hours. Good thing your server is catching that!
But I think 24 hours must be the LND default invoice expiration time. Since LND is widely used and most apps don't let you set a pre-image for the invoice, you're likely to encounter this problem frequently unless you make it clearer in the user interface that a shorter expiration is required.