• 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 Guides, Walkthroughs & Tutorials HAproxy on PFsense (websocket working) Updated Dec24

     
    • 0 Vote(s) - 0 Average

    HAproxy on PFsense (websocket working) Updated Dec24

    Haproxy GUI config on Pfsense with screenshots and examples
    shm0
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2025 Jan
    Reputation: 0
    #5
    2025-01-18, 02:19 AM (This post was last modified: 2025-01-19, 07:51 PM by shm0. Edited 5 times in total.)
    Hi!
    Thank you for this guide.
    I have some questions!
    Doesn't
    http-response set-header Connection "keep-alive"
    override
    http-request set-header Connection "upgrade" if { req.hdr(Upgrade) -i WebSocket }
    ?
    I tried to add some conditional checks (if !{ req.hdr(Upgrade) -i WebSocket }) to the set keep-alive rule but it still breaks websockets on some Smart TV apps.
    And X-Frame-Options "SAMEORIGIN" breaks the LG WebOS App (Black screen after login).

    And these acls:
    jf hdr_connection_upgrade hdr_upgrade_websocket or jf -> will always evaluate to jf
    emby hdr_connection_upgrade hdr_upgrade_websocket or emby -> will always evaluate to emby
    making hdr_connection_upgrade hdr_upgrade_websocket obsolete.

    I'm not sure if it is actually needed to set:
    option http-server-close
    option forwardfor
    and some other options, in both the fronted and backend.
    Is it actually a good idea to enable http-server-close for non websocket traffic?
    The timeouts also seem quite high?

    //edit
    http-server-close actually seems to break websockets for me...
    The only relevant timeout for websockets seems to be the tunnel one.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    Messages In This Thread
    HAproxy on PFsense (websocket working) Updated Dec24 - by gaming09 - 2024-12-01, 07:21 PM
    RE: HAproxy on PFsense (websocket working) Updated Dec24 - by jaillybelly - 2024-12-11, 05:05 AM
    RE: HAproxy on PFsense (websocket working) Updated Dec24 - by gaming09 - 2024-12-11, 05:46 PM
    RE: HAproxy on PFsense (websocket working) Updated Dec24 - by jaillybelly - 2024-12-14, 09:25 PM
    RE: HAproxy on PFsense (websocket working) Updated Dec24 - by shm0 - 2025-01-18, 02:19 AM
    RE: HAproxy on PFsense (websocket working) Updated Dec24 - by dreunion61 - 2025-02-15, 01:20 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