+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Apache2 Proxy SubPath (/t-solved-apache2-proxy-subpath)
Apache2 Proxy SubPath - whoo - 2024-07-20
Hi,
I followed documentation https://jellyfin.org/docs/general/networking/apache
Client -> Apache 2 -> Jellyfin
Apache HTTP Server Project | Works
Apache with Subpath | doesn't work
- BaseURL is set
- i saw requets with tcpdump localhost from apache to fellyfin
- but jellyfin send 404 on /jellyfin/socket
Plateform: Docker
Version: 10.9.7
Regards,
Whoo.
RE: Apache2 Proxy SubPath - TheDreadPirate - 2024-07-20
One of the other mods who uses sub-paths is suggesting you clear your browser cache. Jellyfin caches aggressively and since you accessed your server without the subpath a lot of data may be cached for the non-subpathed URL.
RE: Apache2 Proxy SubPath - whoo - 2024-07-20
Thanks for answering.
- I try to clean cache.
- I try to start a new browser ... without any success.
Subpath works without proxy: http://x.x.x.x:8096/subpath/
Probably an error on configuration, I don't know how to configure debug mode.
W.
RE: Apache2 Proxy SubPath - TheDreadPirate - 2024-07-20
Can you share your apache config via pastebin. Censor the domain.
RE: Apache2 Proxy SubPath - whoo - 2024-07-20
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.
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