• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Extra Nginx Configurations

     
    • 0 Vote(s) - 0 Average

    Extra Nginx Configurations

    config path for nginx access.log in container?
    Anders
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2024 May
    Reputation: 0
    #1
    2024-05-30, 09:57 AM
    I am running Jellyfin in a docker from LinuxServer.IO that is installed through an addon repository from LibreELEC.
    I am also running SWAG from LinuxServer.IO that is installed in the same manner as Jellyfin is. 

    Everything works fine, except for maybe two things. The primary thing is a path question regarding the FAQ/Howto hosted at jellyfin. 
    This in specific  Nginx | Jellyfin 
    Quote:#Must be inside server block
    #Insert into all servers where you want filtering (e.g HTTP + HTTPS block)
    access_log /var/log/nginx/access.log stripsecrets;

    The path for the access_log, what should that one be?
    I have tried with /config/log/nginx/access.log but without any luck.
    The full path to the config is /storage/.kodi/userdata/addon_data/docker.linuxserver.swag/config/log/nginx/access.log but since this is running in a docker, i assume it cannot read outside the docker home path? Which should be  ~/.kodi/userdata/addon_data/docker.linuxserver.swag/
    Anders
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2024 May
    Reputation: 0
    #2
    2024-05-30, 10:47 AM
    Beside the access_log path, where is this configuration snippet about censor api_key supposed to reside?
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #3
    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.

    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.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    niels
    Offline

    Core Team

    Posts: 248
    Threads: 4
    Joined: 2023 Jun
    Reputation: 12
    Country:Netherlands
    #4
    2024-05-30, 08:19 PM
    I would advise against using that snippet as it is wrong. There are currently two ways to send an API key or access token via query parameter and this filter only removes one of them from logs. The ApiKey (note the missing underscore) parameter would still show up.
    [Image: GitHub%20Sponsors-grey?logo=github]
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode