• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting SyncPlay Fails

     
    • 0 Vote(s) - 0 Average

    SyncPlay Fails

    SyncPlay Fails with wss:// Behind Correctly Configured Nginx - Diagnostic Proof Included
    xtendo
    Offline

    Junior Member

    Posts: 5
    Threads: 1
    Joined: 2025 Jun
    Reputation: 0
    #3
    2025-06-29, 09:59 AM
    (2025-06-29, 06:17 AM)niels Wrote: Because you're using a base URL the config needs to be slightly different. Can you share the complete content of your Nginx config (obviously hide your domain from it)

    Thanks so much for taking a look at this, I really appreciate it.

    That's what I suspected as well – that the /jellyfin subpath is the source of this subtle problem. I've tried many configurations, and I'm very interested to see what you think.

    Here is the complete content of my /etc/nginx/apps/jellyfin.conf file. This is the final, stable configuration that allows the main UI to work perfectly, but where SyncPlay (WebSocket) still fails.

    nginx
    # Main Jellyfin UI traffic - subpath /jellyfin
    location /jellyfin {
        # This proxy pass to the HTTP port is correct based on our tests.
        proxy_pass http://127.0.0.1:8096;
        
        proxy_set_header Host $host;
        proxy_http_version 1.1;

        # These headers are for WebSocket support.
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        
        # These headers tell Jellyfin it is behind a proxy.
        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-Ssl on;
        
        proxy_redirect off;
        proxy_buffering off;
    }


    For completeness, and to save you time, here is some additional context:

    The Jellyfin backend is correctly configured for this proxy. The file /etc/jellyfin/network.xml has <BaseUrl>/jellyfin</BaseUrl> set, and internal HTTPS is disabled (<EnableHttps>false</EnableHttps>).

    I also attempted using the advanced map directive in /etc/nginx/nginx.conf to set the Connection header, and I tried temporarily disabling http2 on the main listener. Neither of these attempts fixed the WebSocket issue.

    The core mystery is that a direct curl test to http://127.0.0.1:8096/jellyfin/socket from the server's command line works perfectly, but the same connection fails when proxied through Nginx.

    Thank you again for your help. Please let me know if you see anything out of place or if you need the contents of any other files.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    Messages In This Thread
    SyncPlay Fails - by xtendo - 2025-06-28, 12:00 PM
    RE: SyncPlay Fails - by niels - 2025-06-29, 06:17 AM
    RE: SyncPlay Fails - by xtendo - 2025-06-29, 09:59 AM
    RE: SyncPlay Fails - by niels - 2025-06-29, 10:07 AM
    RE: SyncPlay Fails - by xtendo - 2025-06-29, 11:27 AM
    RE: SyncPlay Fails - by niels - 2025-06-30, 06:21 AM
    RE: SyncPlay Fails - by xtendo - 2025-06-30, 11:57 AM
    RE: SyncPlay Fails - by niels - 2025-06-30, 12:13 PM
    RE: SyncPlay Fails - by xtendo - 2025-06-30, 02:30 PM

    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode