I’ll have a dig through the amethyst source unless it’s something nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z is aware of? 🤔

Reply to this note

Please Login to reply.

Discussion

The app got a http status of 400. Maybe the server was a bit busy? Tor / VPN could also affect this.

BTCPay Server returns a call back url which when followed takes you to the actually invoice url. I’ve just made a change on my server to see if it work. I’ve basically done a rewrite to forward directly to the invoice url.

It seems to work from here. But it was worked before. The 400 status returns before anything else.

Odd, never had an issue with Damus, I’ll have a look though the amethyst code and BTCpay server code over the weekend. If it’s amethyst I’ll fix and raise a PR, if it’s BTCpay server… well… I’ll do the same 🤣

Analysis conducted, I don’t believe it’s an Amethyst issue. 👍