2024-03-27, 05:41 PM
Ah. Not using host networking. You'd have to do additional configuration to allow SWAG to communicate with non-docker services. Or just add "--network host" as one of the parameters so that is uses the same IP and NIC as the host OS and other apps (including Jellyfin). You will need to open port 443 in the host firewall after doing this.
The "Known Proxies" config tells Jellyfin to log the "X-Forwarded-For" field, which would have the original requestor when using a reverse proxy on a different host. Since SWAG and Jellyfin are on the same host, this is not necessary.
The "Known Proxies" config tells Jellyfin to log the "X-Forwarded-For" field, which would have the original requestor when using a reverse proxy on a different host. Since SWAG and Jellyfin are on the same host, this is not necessary.
Jellyfin 10.9.3
Ubuntu 24.04 LTS (bare metal)
Intel i3 12100 on Asus Prime H610M-E D4 mATX
32GB DDR4-3600
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
WD Green 3TB (Samba shares)
WD Red 3TB CMR (WIP Media, Test libraries)
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
Fractal Meshify 2
Corsair CX430
Ubuntu 24.04 LTS (bare metal)
Intel i3 12100 on Asus Prime H610M-E D4 mATX
32GB DDR4-3600
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
WD Green 3TB (Samba shares)
WD Red 3TB CMR (WIP Media, Test libraries)
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
Fractal Meshify 2
Corsair CX430