🐶🐾🫡 Damus gives me error! 
Discussion
Hmmmmmm... Ok checking cloudflare logs thanks for helping
Anytime! 🐶🐾🫡
CORS? 🐶🐾🤔
curl -I https://pay.utxo.one/.well-known/lnurlp/zap
HTTP/2 405
date: Fri, 05 May 2023 01:28:20 GMT
allow: GET
content-security-policy: script-src 'self'
referrer-policy: same-origin
x-content-type-options: nosniff
x-frame-options: DENY
x-xss-protection: 1; mode=block
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=Z637JraaPjTHoe5nChKvqWfwWnmNl7upNtdtXYfOFrruRpGWK4dPf89CSlvKp5iGOdxeLXIQTYqgUYBEw3YzOjip1GpZ8xv3jKMFxYNK6HbgWkPSSk9T2snS8xZxCE8AEqubnhdzZy0BsR4%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
strict-transport-security: max-age=0; includeSubDomains
server: cloudflare
cf-ray: 7c2534c9ba39e04b-NRT
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
In CF panel, go to your Website, Rules, Transform Rules, Modify Response Headers. Add a rule “All Incoming requests “
Add Access-Control-Allow-Origin *
🐶🐾🫡
And zapping you from snort. HTTP-400 (bad request) 🐶🐾🫡
Ok I see it in snort, gonna fix soon! Thank you
Snort console log:
cess to fetch at 'https://pay.utxo.one/.well-known/lnurlp/zap' from origin 'https://snort.social' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values '*, *', but only one is allowed. Have the server send the header with a valid value, or, if an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
CORS! Fucking CORS 🐶🐾😂
You’ll need to disable CF rule. Now you have two CORS headers! 🐶🐾😂😂😂
Ok I think it's working now officially
I am still failing from Damus! Let me try your profile and snort again 🐶🐾🫡
Profile worked🐶🐾🫡 314⚡️
🙏🙏
Damus on Mac worked! Damus on iPhone still failing despite Clear Cache. Let me restart my phone and try! 🐶🐾🫡
I think now it’s cache! I would suggest adding this rule! 🐶🐾🫡
And clear cache for https://pay.utxo.one/* 🐶🐾🫡
Ok purged cache and added page rule! 🫡🫡
This is weird! I still cannot zap your note for whatever reasons. Snort also gives me a strange issue now.
{"status":"ERROR","reason":"Lightning node could not generate invoice with description hash: The HTTP status code of the response was not expected (500)."}
(anony
I think I know why!!!! I cannot zap you as anon or private! 🐶🐾🫡😂
Yes! Public zaps only! Seems that your zapper has issues with anon and private zaps! Use nostdress for real! Or check zapper logs and see why it goes http-500 when anon. Make sure you allow for a 512 chat comment on the invoice! This might be it! 🐶🐾🫡