govperm

Members
  • Posts

    6
  • Joined

  • Last visited

govperm's Achievements

Noob

Noob (1/14)

3

Reputation

  1. updating again... so for whatever reason the nvidia driver (from the apps tab) wasn't installed after I updated from 6.9.1 to 6.9.2... so had to re-install that, added back --runtime=nvidia to both plex and emby dockers and we're back in action. so before starting emby and plex if they show as "stopped" after you update, go install the nvidia driver and set it up before restarting those dockers and you should be ok. But may have to re-install the dockers. I did not have to re-map anything in Plex like the author did. They both fired up straightaway.
  2. can confirm, re-adding --runtime=nvidia back into extra params will crash the docker. So is that extra parameter not needed anymore to allow the docker to use the gpu to transcode? When I'm in emby, it doesn't show the gpu as an available encoder or decoder when set to advanced, so I'm wondering if it's not using it. Also the plugin GPU Statistics is also not re-installing. I only updated from 6.9.1 to 6.9.2. Everything was fine with 6.9.1 with the transcoding/nvidia.
  3. For Emby, you said "deleted the transcoding portion and updated". Just wanted to clarify, in the "edit" for the app, remove --runtime=nvidia from the extra parameters or it won't re-install... Question though, to use the gpu transcoding, we need to put --runtime=nvidia back into extra parameters, correct? Will it cause the docker to crash again? or after you re-install the docker, is it ok to re-input that extra parameter with your gpu info?
  4. I spoke with customer support at PIA, they are now aware that port forwarding on CA Montreal and CA Toronto does not work with their open vpn files. They said it does work with their PIA clients, but they need to figure something out with the open vpn config or something. For now CA Vancouver works, but who knows for how long. Hopefully they fix Toronto and Montreal before they switch to Nextgen for Vancouver and mess it up.
  5. I had to switch to CA Vancouver as well. CA Toronto and CA Montreal weren't allowing the strict port forwarding to be enabled and work properly. I think you're correct that the upgrades are causing issues at the moment. But hopefully they'll figure it out soon.