Avatar
Nunya Bidness 2y ago

#[0]

Nostrgram has been behaving badly all day and yesterday for me.

Opened the console and found 35 instances of this:

"A cross-origin resource sharing (CORS) request was blocked because of invalid or missing response headers of the request or the associated preflight request .

To fix this issue, ensure the response to the CORS request and/or the associated preflight request are not missing headers and use valid header values.

Note that if an opaque response is sufficient, the request's mode can be set to no-cors to fetch the resource with CORS disabled; that way CORS headers are not required but the response content is inaccessible (opaque).

33 requests"

This was after I cleared cookies etc. and reset Alby.

Can't functionally log in and, you know, reach for stuff and do things.

Thought I'd let you know.

Reply to this note

Please Login to reply.

Discussion

Avatar
Derek Ross 2y ago

I can't get it to load either. I've nuked local storage and it still won't load.

Avatar
jleger2023 2y ago

The CORS errors are just failures to fetch Nip05 IDs from sites that won't accept requests from a web app. You can ignore those.

The likely reason you can't access NostrGram is because it's running off a web socket server on port 444. If you have a custom configured firewall it won't allow the request. Check your firewall and see if that port is open. On standard Windows/Mac/phone firewalls it is, but more advanced users might have more advanced lock-downs.

Avatar
jleger2023 2y ago

The CORS errors are just failures to fetch Nip05 IDs from sites that won't accept requests from a web app. You can ignore those.

The likely reason you can't access NostrGram is because it's running off a web socket server on port 444. If you have a custom configured firewall it won't allow the request. Check your firewall and see if that port is open. On standard Windows/Mac/phone firewalls it is, but more advanced users might have more advanced lock-downs.