2024-05-30, 04:17 PM
(This post was last modified: 2024-05-30, 04:19 PM by TheDreadPirate. Edited 1 time in total.)
The api_key censoring config is supposed to get inside the "server" block, which is where all your other configs for Jellyfin reside.
You have to make sure that the log path is correct. You can open a bash session for your SWAG container and find the container path for the log file and then provide that in config to strip secrets.
Code:
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name DOMAIN_NAME;
ANYWHERE IN HERE
......
location /jellyfin/ {
# Proxy main Jellyfin traffic
proxy_pass http://$jellyfin:8096;
...
}
ANYWHERE IN HERE
}
You have to make sure that the log path is correct. You can open a bash session for your SWAG container and find the container path for the log file and then provide that in config to strip secrets.
Jellyfin 10.9.11
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