It seems a CORS problem, plus a weird redirect:

Access to fetch at 'https://basspistol.com/.well-known/lnurlp/setto' from origin 'https://fevela.me' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

GET https://basspistol.com/.well-known/lnurlp/setto net::ERR_FAILED 301 (Moved Permanently)

Reply to this note

Please Login to reply.

Discussion

Interesting, and very strange... So the basspistol com well-known is supposed to be a 301 redirect, never had this problem before. Didn't know there even was cors issues on 301s... 🤔

I get the same error on fevela.me but no other client. Good to know, will explore my options.

CORS should be enabled on your server, I could only use a proxy to bypass the problem. So clients that currently work are A) Non web or B) Use a proxy.

Well... it worked fine on jumble 🤷 But I'm not sure how 😅 Turns out i had my cors rules under the www.basspistol.com domain block, but not on the basspistol.com... It seems to work now!

Many thanks for the heads-up!

It works, zapped!

> it worked fine on jumble

Maybe it has a proxy for that, I need to check the code.