Add reverse proxy configuration

[jellyfin-archive]

Add reverse proxy configuration

[joshuaboniface]

Very good idea - I plan to document the 3 main reverse proxies (Apache, NGiNX, and HAProxy).

[sparky8251]

If we can figure out why those additional apps break for you that would be ideal.

At worst, we can say something like "these configs are known to work with the following apps. if you know how to fix another one, please open an issue on" and link here.

[hawken93]

Here was my end result..
jellyfin/jellyfin#533 (comment)

Using ProxyPass without rewrite rules did not work for me, I had to use rewrite rules to make it pass the get arguments...

So I wanted to ask if you could double check that you are in fact getting 101 on the websocket, not 404...

Furthermore, I found out that if the URL of the server contains "/emby" for example as in "https://emby" then it will connect to /socket instead. So until the code is less weird, it would be safe to support both paths

From what I can tell, the server seems to basically support any path as long as it is a websocket upgrade request.. I could be wrong

[sauerj]

@hawken93 I checked my vhost configuration and these are the http request and response headers.

I had some issues setting up the RewriteRule so as the ProxyPass and ProxyPassReverse directives are working for me, I gave up trying with Rewrite.

GET /embywebsocket?api_key=487116096bb84dbead82ed0807f96b3f&deviceId=TW96aWxsYS81LjAgKFgxMTsgTGludXggeDg2XzY0OyBydjo2MC4wKSBHZWNrby8yMDEwMDEwMSBGaXJlZm94LzYwLjB8MTU0NjQyOTAwNDQwNw11 HTTP/1.1
Host: jellyfin.example.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: de,en-US;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate, br
Sec-WebSocket-Version: 13
Origin: https://jellyfin.example.com
Sec-WebSocket-Extensions: permessage-deflate
Sec-WebSocket-Key: 3gsE0qZVVvp0btM4rvXdkA==
Cookie: ajs_user_id=null; ajs_group_id=null; ajs_anonymous_id=%2200000000000000000000000000%22
DNT: 1
Connection: keep-alive, Upgrade
Pragma: no-cache
Cache-Control: no-cache
Upgrade: websocket

HTTP/1.1 101 Switching Protocols
Connection: Upgrade
Upgrade: websocket
Sec-WebSocket-Accept: aYri2kLjFPZYY1VLtTY+DIbVj3I=

[hawken93]

The only difference is that I didn't have ProxyPassReverse on the websockets, so that must be it :)

[cfunseth]

Any interest in a Traefik configuration? It can handle SSL certs directly and has some nice integrations with Docker using labels.

[JustAMan]

Can you build upon #40? The more options we have the better.

[joshuaboniface]

I'd say this is pretty much done, with all 3 major reverse proxies covered. If someone wants to add more PRs are always welcome!