Kashiro

Members
  • Posts

    10
  • Joined

  • Last visited

Posts posted by Kashiro

  1. 29 minutes ago, ich777 said:

    Haven't looked into it yet.

     

    Dependencies are not missing but ffmpeg needs to be compiled with NVENC support to get this working and I simply haven't got time yet to look into this, anyways Intel and AMD iGPUs/dGPUs should work fine for now.

     

    This is something that is on my to do list but no ETA yet.

     

    Sadly haven't got an iGPU as I'm running on Ryzen. I'll be waiting patiently then :D Thanks!

    • Like 1
  2. On 7/2/2021 at 7:06 PM, ich777 said:

    I will loom into this but give me some time please, I will push the update for now that is working with Intel in the next few days and report back to you what my findings are in Nvidia.

     

    @ich777

     

    Any luck with this?

     

    I'm currently running into the same problem where I'd like to use my P2000 to transcode the Owncast stream. Seems like there are some dependencies missing and ffmpeg needs to be built with nvenc support. 

  3. 2 minutes ago, drzaph said:

    You try clicking the "Web UI" link in the docker container to ensure the address is correct?

     

    Yeah, I'm 100% certain that the url is correct. The thing is though, the Plex server becomes unreachable for every user/device. 


    As soon as I reboot the contrainer the issue is gone again for a little while.

  4. I'm running into this issue where after a period of time my Plex server becomes unreachable. Whenever I try to access the web interface, I get presented with a "503 Service Unavailable" error.

     

    0be82ba3d7.png

     

    The docker itself is still running at that point, and nothing special is showing up in the docker log.

     

    fbc5a937c6.png

     

    The issue goes away after restarting the docker container. This happens about 3-4 times a week. It's a bit annoying having people telling me my Plex server is down multiple times a week.

     

    Any suggestions?

  5. I'm running into some issues with Plex being ssl proxypassed through this docker. I can access the proxypassed page just fine, but then I get a message saying: The server "server" does not allow secure connections, with the option to allow once/always (but both don't actually do anything). When I access Plex directly via LAN it works just fine. My browser is giving me a notification that the page is trying to load unsecure scripts.

     

    What I've tried so far:

     

    - Serving Plex through both http and https via nginx

    - Setting the custom server access urls in Plex settings

    - Setting Secure Connections in Plex: Disabled/Preferred/Required


    Part of the nginx config:

    Quote

     

        location /web {
            # serve the CSS code
            proxy_pass http://192.168.2.3:32400/web;
            include /config/nginx/proxy.conf;
            }

        location /plex {
            # proxy request to plex server
            proxy_pass http://192.168.2.3:32400/web;
            include /config/nginx/proxy.conf;
        }

     

     

    Proxy.conf:

    Quote

    client_max_body_size 10m;
    client_body_buffer_size 128k;

    #Timeout if the real server is dead
    proxy_next_upstream error timeout invalid_header http_500 http_502 http_503;

    # Advanced Proxy Config
    send_timeout 5m;
    proxy_read_timeout 240;
    proxy_send_timeout 240;
    proxy_connect_timeout 240;

    # Basic Proxy Config
    proxy_set_header Host $host:$server_port;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto https;
    proxy_redirect  http://  $scheme://;
    proxy_http_version 1.1;
    proxy_set_header Connection "";
    proxy_cache_bypass $cookie_session;
    proxy_no_cache $cookie_session;
    proxy_buffers 32 4k;
     

     

     

    Is it required to set up a custom certificate within Plex itself? I assumed this wouldn't be necessary, as this docker would take care of the ssl part.

     

  6. 12 minutes ago, itimpi said:

    If you make sure the top level folder corresponding to  a share exists on all disks you want to be part of the share (does not have to have any content) then you will get the right answer.   In practise for the majority of people this will already be the situation so they get the expected result.

     

    It used to be like that for me as well though with 6.3.5.

     

    I've manually created the folders for each Share on each individual drive and it's back to normal now. Thanks for the help!