macem

Members
 View Profile  See their activity

  • Posts

    8

  • Joined

 Content Type 

Posts posted by macem

    No WEBGui after cache ssd's died, so my server is down, please HELP!!

    in General Support

    Posted

    15 hours ago, Chris2NyCE said:

    hey...i found a fix a user posted 6 hours ago...that referred back to a 2018 thread i think;
    Basically, i just pulled my flash drive, popped into into my PC and went into the config folder then SSL...then deleted the entries within the SSL folder. 

     

    Thanks so much for posting this, as it fixed my issue as well!!

     

    My webGUI suddenly didn't launched when I upgraded from 6.10.0-rc3 to 6.10.0-rc4. I guess it might have to do with the SSL cert being expired, which probably by chance ended the same day when I did the upgrade. 

     

    5 hours ago, ChillZwix said:

     

    THANK YOU SO MUCH!! I did delete the files and the webGUI come back after reboot. 

    So easy fix, thank you!! :D

     

    And thanks @ChillZwix for posting this issue, otherwise I would have opened my own topic 😊

    • Like 1

    [Support] Linuxserver.io - Jellyfin

    in Docker Containers

    Posted

    21 hours ago, Phoenix Down said:

    My understanding is that if the Jellyfin app determines that you can play the video without transcoding (i.e. Direct Streaming), it will prefer that to transcoding.

    Here I am reading on the forum, testing everything in browser / Android app and still don't understanding what is happening 🙃 But apparently Jellyfin indeed optimises their replay option. When I tried streaming to Chromecast (which I rarely use), I noticed it started to use streaming, which is also displayed in the Intel GPU Tool. Thanks all for ruling out any possible errors for me and the quick responses!!

    • Like 1

    [Support] Linuxserver.io - Jellyfin

    in Docker Containers

    Posted · Edited by macem

    1 hour ago, aurevo said:

     

    Which CPU model do you use exactly?

     

    I only did the step "modprobe i915" without adding chmod rights.

     

    In the docker extra parameters I only entered the following: "--device=/dev/dri"

     

    In Jellyfin I choose VAAPI and enter this "/dev/dri/renderD128"

     

    Do you only have the integrated GPU or also an external one?

     

     

    Thanks for the quick response! 

     

    I am only using an Intel i5-3470, without any other GPU installed. Changed to what you suggested in the go file without the chmod, and updated the docker extra parameter to '--device=/dev/dri' and rebooted the server. In Jellyfin my setting for VAAPI is '/dev/dri/renderD128'.

     

    After the reboot I was still able to enter the folder and also the command in _Console did start the HW enabled transcoding. But when playing from the Android App, it still uses the CPU with 'Direct Play' instead of the HW transcoding.

     

    Only thing I noticed is that you suggest the extra parameter as '--device=/dev/dri', while I am using a [space] after the [=] sign, which would result in '--device=/dev/dri'. When I tried to remove this space before, I would get an error and needed to reinstall the docker, but now I am able to save the docker. The result however is only a change from 'Direct Play' to 'Direct Streaming', but still without using the HW transcoding when looking at Intel GPU Tools. 

     

     

    [Support] Linuxserver.io - Jellyfin

    in Docker Containers

    Posted

    I am also "one of them" spending my whole day trying to get HW transcoding to work 😏

    As far as I can tell, I did all the recommendations in the various threats, but when I play a .mkv I don't see my HW is being used.

     

    What I did so far:

    1. I am using an Intel CPU with QuickSync support
    2. Added the following to my go file using the CA Config File editor and rebooted Unraid
      • modprobe i915
      • chmod -R 777 /dev/dri
    3. Added --device=/dev/dri:/dev/dri to the extra parameters of the Jellyfin docker
    4. Enabled HW transcoding, using VAAPI and restarted Jellyfin
    5. When I hit the command /dev/dri I can access the folder (both from the server Terminal aswell in the Jellyfin _Console)
    6. When I hit the command in the Jellyfin _Console for a HW transcode (thanks @sir_storealot), I see it starts using the HW transcoder using the Intel GPU tools
    7. Even updated from Unraid 6.8.0 to Unraid 6.9.0 b35,rebooted the server, and hit the command to enable i915 support and did steps 5 and 6 again

    When I however start playing the same .mkv from the web-browser or the Android app of Jellyfin, it only uses my CPU and shows 'Direct Play'. When I look at the Intel GPU tools, it is also only using the CPU instead of the engine.

     

    Sorry for the details, but wanted to show what I did and not just gave up the first time it didn't work...

    Any suggestions what I am missing here?

    [support] macesters's Docker Repository

    in Docker Containers

    Posted

    On 11/7/2020 at 1:22 AM, jbquintal said:

    I had the same issue.  The only fix is to rollback the firmware on your APs or wait until Mace updates the docker app.  The latest firmware needs "Omada controller v4.1.5" to work properly and show stats.  However, Mace's docker app only has EAP-Controller v3.2.9. 

    I actually hope Mace's actually keeps the EAP-Controller supported for v3.2.10 as it stands, as the upgrade to the Omada Controler v4.x.x doesn't support older v1 access points (like me). See more details on compatibility support over here: https://www.tp-link.com/en/omada-sdn/compatibility/

     

    In case Mace (or someone else) would like to add support for v4.x.x anyway, either let there be an option to continu using v3.2.10 or create a second Docker.