My clanker suspects it was a Cloudflare issue with your server:
Amethyst hits this error while fetching the zap invoice, before it ever talks to her NWC connection, so her Coinos wallet never
gets involved.
What I checked on defauxking@onyxcatpottery.com:
- https://onyxcatpottery.com/.well-known/lnurlp/defauxking is a static file copied from Alby, served by LiteSpeed behind Cloudflare. It still points everything at getalby.com (the callback,
and the identifier defauxking@getalby.com).
- It sends no Content-Type header at all. The body should be served as application/json. This is the most likely thing to trip Amethyst's parser.
- Fetched from here, the body is valid JSON, with the same result under Android user agents (okhttp, Amethyst, Android). I got no Cloudflare challenge page, but I can't rule one out for her
IP or region. That would also produce "Error Parsing JSON."
- The Alby callback works: it returned a valid invoice for 21 sats, and it supports Nostr zaps.
What the recipient should do: set Content-Type: application/json on /.well-known/lnurlp/* in LiteSpeed/.htaccess, and make sure Cloudflare's bot protection skips that path. Or they could
just use defauxking@getalby.com directly. Their copied file also won't pick up any changes Alby makes later.
Adam Soltys
npub1nz…uz7rp
2026-09-17 14:57:01 UTC
in reply to nevent1q…vwk7
Author Public Key
npub1nzhym2fxc3cuy073950tm4vrnw5zj9a65cvwrp8qexgkmy7u7nmssuz7rpSeen on
wss://relay.coinos.ioPublished at
2026-09-17 14:57:01 UTCEvent JSON
{
"id": "5aecad1fa939568211e5c0a64f7ae6e63e7801c5548df6ce140e619bd4b51f6e",
"pubkey": "98ae4da926c471c23fd12d1ebdd5839ba82917baa618e184e0c9916d93dcf4f7",
"created_at": 1789657021,
"kind": 1,
"tags": [
[
"e",
"9f388b08dd776087cf933b94663537365129737b2cbebce945e00471854b0aa2",
"",
"root"
],
[
"e",
"000064967df4043d65a8568ce83cb2e524b68b04000292722f7a2da42a62f647",
"",
"reply"
],
[
"p",
"3bbcab7e3d2b07a55027206d5e193813f01406882daad05412389a50b67ba92e"
],
[
"p",
"ba18b6545357cff8e531accfe1d609a41ef3023fba071db1cbf5a67448c19046"
],
[
"client",
"coinos"
]
],
"content": "My clanker suspects it was a Cloudflare issue with your server:\n\nAmethyst hits this error while fetching the zap invoice, before it ever talks to her NWC connection, so her Coinos wallet never\n gets involved.\n\n What I checked on defauxking@onyxcatpottery.com:\n - https://onyxcatpottery.com/.well-known/lnurlp/defauxking is a static file copied from Alby, served by LiteSpeed behind Cloudflare. It still points everything at getalby.com (the callback,\n and the identifier defauxking@getalby.com).\n - It sends no Content-Type header at all. The body should be served as application/json. This is the most likely thing to trip Amethyst's parser.\n - Fetched from here, the body is valid JSON, with the same result under Android user agents (okhttp, Amethyst, Android). I got no Cloudflare challenge page, but I can't rule one out for her\n IP or region. That would also produce \"Error Parsing JSON.\"\n - The Alby callback works: it returned a valid invoice for 21 sats, and it supports Nostr zaps.\n\n What the recipient should do: set Content-Type: application/json on /.well-known/lnurlp/* in LiteSpeed/.htaccess, and make sure Cloudflare's bot protection skips that path. Or they could\n just use defauxking@getalby.com directly. Their copied file also won't pick up any changes Alby makes later.",
"sig": "a0d2aacbf6fd242776d92ee7717462116f4b6713ec4b7301345dd0674a369327f47241875eef0f93f5b4c3c7a2fd962b0f492071ac27a1c58f179b89e810c07f"
}