timeline doesn't update anymore

[haayman]

I'm running from https://main.elk.zone/ with the latest commit bfd05f7
The home timeline is not updating automatically anymore. I have to reload the page to get the latest posts. Anyone else seeing this?

In the network tab I see a websocket to /api/v1/streaming with this message

and there's also a 404 error message for /api/v1/push/subscription

[athosmoreno]

I am also experiencing this on canary, both on main.elk.zone and on Elk self-hosted instances running on canary version with any browser I try.

The stable instance does not even let me authenticate with my current Mastodon server.

[cadusilva]

For me the error says 401 - Unauthorized. Happens with Mastodon and also GoToSocial.

And even when logged out, there's this error on the browser Console:

GET wss://m.webtoo.ls/api/v1/streaming NS_ERROR_WEBSOCKET_CONNECTION_REFUSED
LibreWolf can’t establish a connection to the server at wss://m.webtoo.ls/api/v1/streaming.

The error is always the same, appearing ad infinitum, the only thing that changes is of course the instance URL when logged in. Mastodon webUI works normally without any similar errors. The same thing is true for Pinafore/Semaphore/Enafore, no errors about wss:// and the timeline streams normally.

Phanpy shows similar errors, but there's some fallback route that makes the timeline stream normally.

[cairobraga]

I'm having the same issue, like @cadusilva described, also on LibreWolf (138.0.1-2, Ubuntu 24.04). In my case, I can't even login to my instance: as soon as I go thru OAuth, when it comes back to main.elk.zone, there's a "TypeError: NetworkError when attempting to fetch resource." where the timeline should be and the login didn't really work.

On the browser console a lot of these errors appear:
"Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://gts.cairobraga.com/api/v1/preferences. (Reason: header ‘authorization’ is not allowed according to header ‘Access-Control-Allow-Headers’ from CORS preflight response)."

When I check if cross-site cookies are enabled between elk.zone and my instance on LibreWolf, they are.

Then I decided to try on Firefox: everything works normally.

So I'm guessing it might be a LibreWolf issue.

Oh, and the exact same things happen with Phanpy (cheeaun/phanpy#1153).