mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-24 07:30:57 +01:00
Allow to debug KnownProxies #6842
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#6842
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bdovaz on GitHub (Mar 24, 2025).
I am configuring Swag + Jellyfin + Authelia and I have a problem with the
X-Forwarded-*headers not being processed as it says here:https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/proxy-load-balancer?view=aspnetcore-9.0#forwarded-headers
The problem is that I don't know what happens in this method because there is no logger configured....
516754c2a6/Jellyfin.Server/Extensions/ApiServiceCollectionExtensions.cs (L272)I guess there is no way to debug all this if not creating a PR with
logger.LogDebug()calls right? I guess it would be very useful because otherwise you go blindly without knowing if the value configured inAdvanced -> Networking -> Known proxiesis correct.@jellyfin-bot commented on GitHub (Jul 22, 2025):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@bdovaz commented on GitHub (Jul 22, 2025):
Still relevant