Handshake status 404 Not Found

[JBlocklove]

My connection to my jellyfin server was working perfectly fine until I restarted Mopidy so it could pull in a new playlist I made on jellyfin (not sure if there's a better way to do that, but it sort of worked). When it restarted, the updated playlist showed up but nothing would play. I restarted it in a terminal to see the output logs and this message started showing up:

ERROR    2023-02-09 11:22:51,320 [4207:Thread-5] mopidy_jellyfin.ws_client
  Handshake status 404 Not Found
ERROR    2023-02-09 11:22:51,321 [4207:Thread-5] websocket
  Handshake status 404 Not Found - goodbye

My config never changed and the URL I have in the config is still perfectly accessible through a browser or any of a number of means (android app, jellyfinmediaplayer program, finamp). I'm not really sure what's going on here, but nothing I've tried so far seems to have resolved it.

Things I've tried:

• Uninstalling and reinstalling the Mopidy-Jellyfin plugin
• Rebooting my PC
• Doing a full system update (Arch Linux 6.1.10-arch1)
• Disabling and enabling the plugin in my config
• Clearing the mopidy cache (removing ~/.cache/mopidy)
• Switching to a new wifi network

It seems to work to some extent because every time I start it the library information gets pulled in just fine (playlists, artists, etc.), but when I try to play a song nothing happens and this error just keeps repeating.

[ebiscaia]

I can say that in my case I am having the same errors but I can play my songs.

Another thing I observed is that it only happens when I try to connect to it through my reverse proxy. I just tried to connect to my jellyfin instance using the internal ip + port and there are no messages whatsoever.

Hope this piece of information helps.

[JBlocklove]

It seems I'm able to play my songs again as well, despite the error still showing up. I suppose that might have been an unrelated issue that just happened to show up around the same time.

I'm also using a reverse proxy to connect to Jellyfin, so I imagine that's where this issue is coming from. It doesn't seem to be a breaking issue in any way, but I'll still leave this open for now, as random errors still probably aren't great to have floating around.

[ebiscaia]

Ok,

I managed to solve my case going to Jellyfin website and adding these lines to my reverse proxy (nginx):

location /socket {
        # Proxy Jellyfin Websockets traffic
        proxy_pass http://$jellyfin:8096;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Protocol $scheme;
        proxy_set_header X-Forwarded-Host $http_host;
    }

The page that contains this info is here