Subnostr

Replying to

utxo the webmaster 🧑‍💻

Hmmmmmm... Ok checking cloudflare logs thanks for helping

The Fishcake (nostr.build) 2y ago

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

Reply to this note

Please Login to reply.

Discussion

The Fishcake (nostr.build) 2y ago

In CF panel, go to your Website, Rules, Transform Rules, Modify Response Headers. Add a rule “All Incoming requests “

Add Access-Control-Allow-Origin *

🐶🐾🫡

The Fishcake (nostr.build) 2y ago

And zapping you from snort. HTTP-400 (bad request) 🐶🐾🫡

utxo the webmaster 🧑‍💻 2y ago

Ok thanks can you try now?

The Fishcake (nostr.build) 2y ago

Same problem! Did you clear cache? 🐶🐾🫡

utxo the webmaster 🧑‍💻 2y ago

Ok I see it in snort, gonna fix soon! Thank you

The Fishcake (nostr.build) 2y ago

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! 🐶🐾😂😂😂

utxo the webmaster 🧑‍💻 2y ago

Ok I think it's working now officially

The Fishcake (nostr.build) 2y ago

I am still failing from Damus! Let me try your profile and snort again 🐶🐾🫡

The Fishcake (nostr.build) 2y ago

Profile worked🐶🐾🫡 314⚡️

utxo the webmaster 🧑‍💻 2y ago

🙏🙏

The Fishcake (nostr.build) 2y ago

Damus on Mac worked! Damus on iPhone still failing despite Clear Cache. Let me restart my phone and try! 🐶🐾🫡

The Fishcake (nostr.build) 2y ago

I think now it’s cache! I would suggest adding this rule! 🐶🐾🫡

The Fishcake (nostr.build) 2y ago

And clear cache for https://pay.utxo.one/* 🐶🐾🫡

utxo the webmaster 🧑‍💻 2y ago

Ok purged cache and added page rule! 🫡🫡

The Fishcake (nostr.build) 2y ago

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! 🐶🐾🫡😂

The Fishcake (nostr.build) 2y ago

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! 🐶🐾🫡

utxo the webmaster 🧑‍💻 2y ago

Ah ok I'll bring this up with the team. I am a btcpayserver dev I have to stay loyal 🫡🫡

The Fishcake (nostr.build) 2y ago

🐶🐾🫡 understandable! We better fix it! That was fun troubleshooting! Thank you! Real pleasure! 🐶🐾🫡🫂