Jump to content

aptalca

Community Developer
  • Content Count

    2239
  • Joined

  • Last visited

Community Reputation

127 Very Good

4 Followers

About aptalca

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. aptalca

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    We don't really recommend it for security reasons, but if you really want to, you can edit one of the existing ones and use the unraid ip and port in the proxy_pass directive to proxy via the subdomain method
  2. aptalca

    [Plugin] Linuxserver.io - Unraid Nvidia

    Plex only does hardware encode with Nvidia, not decode. Your cpu is maxing out trying to software decode the 4k stream. Nothing we can do until Plex adds ability to hardware decode. Emby does both encode and decode via hardware with Nvidia.
  3. aptalca

    [Support] Linuxserver.io - Plex Media Server

    I started hitting the transcoder issue as well. The reason I didn't notice it before is because it works fine on mp4. But mkvs cause a transcoder error. Since it works for mp4s I'm convinced it's the new Plex server 1.15 and not docker related. Tag 168 is unable to update to 1.15 (due to change in package location on Plex servers) and that's why it works fine. EDIT: some mkvs play fine, I'm at a loss. Most likely plex transcoder issues. They do use a newer ffmpeg build in 1.15
  4. aptalca

    [Plugin] Linuxserver.io - Unraid Nvidia

    From the first page. . .
  5. aptalca

    [Support] Linuxserver.io - Plex Media Server

    Most of our images don't update apps inside the container so not updating the image for a month is ok. But for apps that update inside the container like this plexpass version, you should make sure you are always on the latest image, otherwise it may break (like it did this time but could have been a lot worse)
  6. aptalca

    [Support] Linuxserver.io - Plex Media Server

    Judging by that log, you need to update your plex image/container
  7. aptalca

    [Support] Linuxserver.io - Plex Media Server

    I didn't notice any issues on my end and had a bunch of users streaming happily over the last few days. No complaints so far.
  8. aptalca

    [Support] Linuxserver.io - OpenVPN-AS

    Umm, that's a no. In bridge mode, connection goes from whatever network unraid uses, to the docker network, to the container through mapped ports, and inside the container it goes to the tun device. The tun device is not exposed to the host. I assure you my unraid knows nothing about a tun device and I have no problems connecting to vpn inside the container. Like I said before, you should test it instead of just hypothesizing.
  9. aptalca

    [Support] Linuxserver.io - Plex Media Server

    Definitely a plex issue and you should ask on their forums
  10. aptalca

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Likely the symlinks got messed up during the restore process. How exactly did you restore?
  11. aptalca

    [Plugin] Linuxserver.io - Unraid Nvidia

    Plex started calling plexpass releases beta releases, so they are now interchangeable
  12. aptalca

    [Plugin] Linuxserver.io - Unraid Nvidia

    1.15 you can check on plex downloads page on their website and toggle between regular and plexpass
  13. aptalca

    [Plugin] Linuxserver.io - Unraid Nvidia

    Did you remove the device mapping? Also make sure it is not in privileged mode. Both of those will let plex see the igpu. Without them, plex won't even know the igpu is there
  14. aptalca

    [Plugin] Linuxserver.io - Unraid Nvidia

    Sometime after 6.7.0 is released, an Nvidia version of it will be compiled by lsio and will be available in the addon. As long as you select it inside the addon, it will update to the Nvidia version of 6.7.0