2024-07-20, 11:09 PM
(This post was last modified: 2024-07-20, 11:40 PM by whoo. Edited 7 times in total.)
Hi,
After successfully testing with Caddy to validate my Jellyfin configuration, I found a workaround.
I have many subpath software, SSL authentication, password authentication (as backup auth), so:
--> multiple sources of conflicts.
No more 404 on /jellyfin/socket
Whoo
After successfully testing with Caddy to validate my Jellyfin configuration, I found a workaround.
I have many subpath software, SSL authentication, password authentication (as backup auth), so:
--> multiple sources of conflicts.
Code:
### when upgrade to websocket redirect with proxy
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule "^/vidz/(.*)$" ws://127.0.0.1:8096/vidz/$1 [QSA,P,L]
###
RewriteRule "^/vidz/(.*)$" http://127.0.0.1:8096/vidz/$1 [QSA,P,L]No more 404 on /jellyfin/socket
Whoo