+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: SOLVED: Blurred Posters behind Caddy reverse proxy (/t-solved-blurred-posters-behind-caddy-reverse-proxy)
Blurred Posters behind Caddy reverse proxy - stillyahoo - 2024-11-09
SOLVED: Seeing as caddy is on same lan as jellfyfin I thought all access was local. But going to Advanced > Netowrking > Remote Access Settings - If i allow remote connections it fixes the issue and all the thumbnails/posters display correctly when accessed through the web. I did also add the caddy local IP address to 'known proxies' but it doesnt seem necessary as withtout it, still works as long as I have enabeld allow remote conection
I have my own domain using cloudflare nameservers. Using cloudflare proxy to point to my IP at server location.
I am running caddy (LXC) as reverse proxy for jellyfin server (LXC) [both in same subnet] and when accesing through web via reverse proxy all the thumbnails for all media are blurred. All the media plays properly though, there is no problem there.
However when accessing jelly through local IP all thumbnails for media are correctly displayed as usual.
I havent changed much in Jellyfin, left the config as it came So im not sure which configurations to list here to show everyone.
my caddyfile entry for jelly is simply
Code:
'domain for jelly' {
reverse_proxy [jelly local IP address:8096]
}Nextcloud is also behind caddy reverse proxy and is working normally.
I have been searching around for a solution for a while but all similiar'ish search results tend to point to docker and nginx modificatios which I cant find correlation for with my proxmox lxc caddy setup.
Any pointers wiould be greatly appreciated.
I remember some settings for metadata savers and saving artwork in media folders would that be of any helpin this situation?
I may have domain names and servers and containers setup with reverse proxies etc but I barely know what I am doing and have somehow bumbled my way through groping in the dark this far, loooool. So my knwoledge is not enough to solve this issue.
RE: Blurred Posters behind Caddy reverse proxy - TheDreadPirate - 2024-11-09
Serving video through cloudflare is against their TOS. We recommend you switch to DNS only.
Also, which client are you using? A browser or Jellyfin Media Player?
RE: Blurred Posters behind Caddy reverse proxy - stillyahoo - 2024-11-09
Hi, I may have misrepresented my setup. The cloudflare is just for DNS, I registered the domain off godady but have cloudflare handle the DNS and that required me to enter clouflare namservers ito the godaddy management page of my domain. I dont use any other service or hosting.
When connecting locally I use the desktop app and browser and both operate 100% accessing Jellyfin through local lan.
When trying to access through web I am using a browser and that is when I have the blurred posters throuhgout.
RE: Blurred Posters behind Caddy reverse proxy - stillyahoo - 2024-11-09
Sorry everyone I am a moron!!!
I thought that seeing as my requests were coming through my reverse proxy on my own LAN I though it was all 'local' traffic.
In Advanced > Netowrking > Remote Access Settings - If i allow remote connections it fixes the issue and all the posters display correctly when accessed through the web
RE: Blurred Posters behind Caddy reverse proxy - stillyahoo - 2024-11-09
(2024-11-09, 02:12 AM)TheDreadPirate Wrote: Serving video through cloudflare is against their TOS. We recommend you switch to DNS only.
Sorry to pester you but you have made me a little concerned, I am uncertain of a lot of things, Im only recently just learning about DNS and https and all things networking and servers. All of this stuff that I am doing is more for experimentation and 'fun' rather than actually putting anything into production.
On my server, I have proxmox with containers and VM's for my Nextcloud/Jellyfin/Tailscale/Openmediavault/Caddy
So with the free cloudflare tier I have Proxied Records for my DNS. I can proxy my A records and CNAME records. If those records are pointing to my jellyfin server is that against the Cloudlfare TOS?
But if I remove the 'proxied' option for the records in DNS settings is it OK? But then is it s good idea to have my personal static IP exposed like that?
I'm honestly not that bothered about having jellyfin accesible through the web, this server build is just for my 'hobby' tinkering and to learn stuff I find intersting. But its not job or profession related.
RE: Blurred Posters behind Caddy reverse proxy - TheDreadPirate - 2024-11-09
If the status is "Proxied" for any service that streams videos (Jellyfin), that is against their TOS. They have a PAID tier for that. Switching it to DNS Only is ok (this is what I do). For OTHER services that are not video streaming, it is OK for them to be proxied.
RE: Blurred Posters behind Caddy reverse proxy - stillyahoo - 2024-11-09
So I have only one IP adress.
It has an A record for the root "mydomain.com"
and CNAMES for each service I run. eg jellyfin.mydomain.com, nextcloud.mydomain.com
Is it OK to proxy the A record for root domain and any other CNAMES I want as long as I dont proxy the jelllyfin CNAME? But isnt the jellyfin CNAME pointing to that root domain? This is the bit I dont really understand.
Or because "jellyfin" CNAME is pointing to root domain, I also HAVE to UN-proxy the root "mydomain.com" A Record?
In cloudflare when I mix and match proxied and unproxied records it gives me the warning triangle saying that some records can expose the IP of others.
I clearly dont really understand what happens in and around DNS servers in terms of records, traffic and requests
RE: Blurred Posters behind Caddy reverse proxy - TheDreadPirate - 2024-11-09
If the CNAME is DNS only it will be DNS only, even if the A or AAAA record it points to is proxied.
RE: Blurred Posters behind Caddy reverse proxy - stillyahoo - 2024-11-09
(2024-11-09, 05:41 PM)TheDreadPirate Wrote: If the CNAME is DNS only it will be DNS only, even if the A or AAAA record it points to is proxied.
Thank you for making that clear, really appreciate it. I didnt know it worked like that