ich777

Ist das wirklich notwendige bzw. warum? Kannst du nicht einfach native die Ports nach außen mit socat frei geben ohne Nginx-Proxy-Manager? Ich hab das nie verstanden bzw. versteh es noch immer nicht warum man game traffic durch einen reverse proxy routet, das bringt nichts außer im schlimmsten Fall Probleme...

I think then it would be best that you post this issue in the according support thread for the Docker container since this is not an issue with the plugin itself. Please note that I always recommend to use the official Plex container, I got a few reports that some of the 3rd party containers won't work properly sometimes with HW transcoding.

Where does the script run? On Unraid itself? If yes, stop the container with: docker stop CONTAINERNAME (of course replace CONTAINERNAME with the container name - case sensitive!) You should be able of course to use this from the Python script for example for Python3 implement this: os.system('docker stop CONTAINERNAME') (for this you have to of corse import os to your Python script) To start the container again simply run: docker start CONTAINERNAME Hope that helps.

I've tried it now on my server and over here this is not the case. Have you changed anything in the template?

At what stage does it stop? Maybe GitHub has again some issues. Do you have a AdBlocker somewhere on your network?

What have you done in there? Click in Add Server at the Favorites tab, enter your server IP followed by the port like: 192.168.178.1:27015 and click Add. After that click on Refresh and your server should be listed if it‘s running. No, I just pulled a fresh copy from the CA App and left everything at default and as you can see from my log it is running just fine.

Do you have a active Internet connection on boot? I think I don‘t understand completely what you‘ve done so far… What I would do in your case is that you boot into safe mode, turn off autostart, reboot again and boot as usual, remove the ZFS Plugin, reboot again, install the ZFS Plugin and after that successfully finishes you should be able to start the Array (I would recommend that you before starting the Array that you open up a Unraid terminal and see if the command „zpool“ is available). @Marshalleq the modules/package should be built after about an hour after a new Unraid version was released if everything went well.

Genau, wegen dem hab ich das ja so gemacht. Das macht nix, der key ist wichtig (aber nichts daran ändern).

Nein. Nein.

Please remove your steam credentials from the templete, they are only needed when they are visible to the user by default and are not hidden at the „Show more …“ section and are marked with the red asterisk * Maybe that is the issue on your system. Anyways if it is now running it should be visible in the Steam Server Browser, I think above you where talking about the in game list or am I wrong?

Does it work on 6.10.3? I have a Nvidia T400 here and it runs fine on both 6.11.0-rc4 and also on 6.10.3 with the latest driver installed.

Do you made sure that you've are on the latest BIOS revision from your motherboard? I had some issues with the first and second gen Ryzen chips here back in the days and I think @SiRMarlon had a similar issue like you do, he ultimately resolved this by completely turning off all power saving features IIRC. The card drops from the bus because some motherboards have pretty aggressive power saving mechanisms in place from which some devices can't recover. You can however test what happens when you issue: nvidia-persistenced from a Unraid terminal, but TBH I don't think that will help. Search in your BIOS for PCI/PCIe based power saving options and disable all of them.

But then it's not the same issue like from above, the user from above also had to use the legacy driver in order to make the card visible to the system because this card is simply "old". You are on the newest driver version from what I see in your log and the card is initialized fine: Sep 4 08:10:59 Vidas kernel: nvidia: loading out-of-tree module taints kernel. Sep 4 08:10:59 Vidas kernel: nvidia: module license 'NVIDIA' taints kernel. Sep 4 08:10:59 Vidas kernel: Disabling lock debugging due to kernel taint Sep 4 08:10:59 Vidas kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 242 Sep 4 08:10:59 Vidas kernel: nvidia 0000:0b:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem Sep 4 08:10:59 Vidas kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 Sep 4 08:10:59 Vidas kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 515.65.01 Wed Jul 20 13:43:59 UTC 2022 Sep 4 08:10:59 Vidas kernel: [drm] [nvidia-drm] [GPU ID 0x00000b00] Loading driver Sep 4 08:10:59 Vidas kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:0b:00.0 on minor 0 What is the output from nvidia-smi? Please also post a screenshot form the plugin page. Do you have C-States enabled in your BIOS? On what BIOS version are you? make also sure that you enable Above 4G Decoding. Is this the first time you are installing the driver?

Does it now loop too after reinstalling the game? If not, it seems that it‘s now fully started and waiting for connections. Can you post a Screenshot from your Docker template please? On what hardware are you trying to run Insurgency?

I think I don‘t understand the wuestion entirely… You ahve a hardware Device which is needed to unlock you Wallet? If yes, I wont recommend to use the container because yes, you described basically what is needed to unlock the wallet and you also have to pass through the hardware key to the container. The container is was mostly designed for poeple which have a Wallet with a passphrase and a keyfile.

Same card and same driver? Have you seen that the user from above has bount the card to VFIO which obviously can’t work? Without the Diagnostics I can‘t tell much…

Not really… But better is always relative. I think the TBS cards are really well built and working great usually. You can look into DigitalDevices but they are a bit more expensive…

I would recommend that you stick with a TBS6902 but keep in mind that currently the TBS6902 drivers doesn't compile on Kernel 5.19 which Unraid 6.11.0-rc4 is based on but it however should be supported by the LibreELEC driver package so you should be good to go.

I think you can see why it's not working: 04:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK110B [GeForce GTX 780 Ti] [10de:100a] (rev a1) Subsystem: eVga.com. Corp. GK110B [GeForce GTX 780 Ti] [3842:2884] Kernel driver in use: vfio-pci Kernel modules: nvidia_drm, nvidia I don't know why but you have bound the card to VFIO in your syslinux.config This is a pretty bad choice if you want to use it for Plex HW transcoding... This card isn't even capable of h265 (HEVC). I would rather recommend that you look into something like a NVIDIA T400, this card is Turing based, has a maximum power draw from 35W, doesn't need external power and you can get it for about $ ~120,- brand new.

Why should it disappear? What if you want to change the package that you've downloaded how would you do that if it disappeared? I really can't tell what's going on there: Sep 3 14:23:40 DataTower kernel: cx23885: cx23885 driver version 0.0.4 loaded Sep 3 14:23:40 DataTower kernel: cx23885: CORE cx23885[0]: subsystem: d471:9022, board: TeVii S471 [card=35,autodetected] Sep 3 14:23:40 DataTower kernel: cx23885: cx23885_dvb_register() allocating 1 frontend(s) Sep 3 14:23:40 DataTower kernel: cx23885: cx23885[0]: cx23885 based dvb card Sep 3 14:23:40 DataTower kernel: Invalid probe, probably not a DS3000 Sep 3 14:23:40 DataTower kernel: cx23885: cx23885[0]: frontend initialization failed Sep 3 14:23:40 DataTower kernel: cx23885: cx23885_dvb_register() dvb_register failed err = -22 Sep 3 14:23:40 DataTower kernel: cx23885: cx23885_dev_setup() Failed to register dvb adapters on VID_B Sep 3 14:23:40 DataTower kernel: cx23885: cx23885_dev_checkrevision() Hardware revision = 0xa5 Sep 3 14:23:40 DataTower kernel: cx23885: cx23885[0]/0: found at 0000:06:00.0, rev: 4, irq: 37, latency: 0, mmio: 0xfe000000 Maybe the card is broken now if it was the case that you've noticed it one day... Now the card is properly detected from what I see: Sep 3 14:23:40 DataTower kernel: cx23885: CORE cx23885[0]: subsystem: d471:9022, board: TeVii S471 [card=35,autodetected] But it fails somehow to register on your server: Sep 3 14:23:40 DataTower kernel: Invalid probe, probably not a DS3000 Did you change anything else on your server? Usually a card won't disappear if you do nothing except it is somehow defective now. BIOS update, swap some PCIe slots for cards or anything else? If the card stopped working with the driver which was installed before my best bet is now that it somehow got defective now... Maybe there was a thunderstorm or something like that which caused this or similar. Do you have another computer where you can test the card in?

Remove just this part, otherwise you would have a bad time… 😅

Please remove the option from your syslinux command line for this card, something seems wrong: Sep 2 22:09:17 DataTower kernel: cx23885: cx23885 driver version 0.0.4 loaded Sep 2 22:09:17 DataTower kernel: cx23885: CORE cx23885[0]: subsystem: d471:9022, board: TeVii S471 [card=35,insmod option] Sep 2 22:09:17 DataTower kernel: cx23885: cx23885_dvb_register() allocating 1 frontend(s) Sep 2 22:09:17 DataTower kernel: cx23885: cx23885[0]: cx23885 based dvb card Sep 2 22:09:17 DataTower kernel: Invalid probe, probably not a DS3000 Sep 2 22:09:17 DataTower kernel: cx23885: cx23885[0]: frontend initialization failed Sep 2 22:09:17 DataTower kernel: cx23885: cx23885_dvb_register() dvb_register failed err = -22 Sep 2 22:09:17 DataTower kernel: cx23885: cx23885_dev_setup() Failed to register dvb adapters on VID_B Sep 2 22:09:17 DataTower kernel: cx23885: cx23885_dev_checkrevision() Hardware revision = 0xa5 Sep 2 22:09:17 DataTower kernel: cx23885: cx23885[0]/0: found at 0000:06:00.0, rev: 4, irq: 37, latency: 0, mmio: 0xfe000000

From what I see the TeVii S471 DVB-S2 PCIe is recognized just fine and should work just fine. For what's happening with your USB device I really can't tell what's going on there, it seems that it loads fine: Sep 2 22:09:19 DataTower kernel: usbcore: registered new interface driver em28xx Sep 2 22:09:19 DataTower kernel: em28xx 1-9:1.0: Binding DVB extension Sep 2 22:09:19 DataTower kernel: i2c i2c-11: Added multiplexed i2c bus 12 Sep 2 22:09:19 DataTower kernel: si2168 11-0064: Silicon Labs Si2168-B40 successfully identified Sep 2 22:09:19 DataTower kernel: si2168 11-0064: firmware version: B 4.0.2 Sep 2 22:09:19 DataTower kernel: si2157 12-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached Sep 2 22:09:19 DataTower kernel: dvbdev: DVB: registering new adapter (1-9:1.0) Sep 2 22:09:19 DataTower kernel: em28xx 1-9:1.0: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)... Sep 2 22:09:19 DataTower kernel: dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered. Sep 2 22:09:19 DataTower kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered. Sep 2 22:09:19 DataTower kernel: em28xx 1-9:1.0: DVB extension successfully initialized Sep 2 22:09:19 DataTower kernel: em28xx: Registered (Em28xx dvb Extension) extension Sep 2 22:09:19 DataTower kernel: em28xx 1-9:1.0: Registering input extension Sep 2 22:09:19 DataTower kernel: Registered IR keymap rc-pinnacle-pctv-hd Sep 2 22:09:19 DataTower kernel: rc rc0: PCTV tripleStick (292e) as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/usb1/1-9/1-9:1.0/rc/rc0 Sep 2 22:09:19 DataTower kernel: input: PCTV tripleStick (292e) as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/usb1/1-9/1-9:1.0/rc/rc0/input3 Sep 2 22:09:19 DataTower kernel: em28xx 1-9:1.0: Input extension successfully initialized Sep 2 22:09:19 DataTower kernel: em28xx: Registered (Em28xx Input Extension) extension Have you yet tried to reboot?

Can you provide your Diagnostics? Without them I can‘t tell much.

If you have only one folder in there it‘s not installed correctly. This is usually a indication that it not installed fully. The steamapps folder is created while downloading, when the game is fully downloaded the files get moved from the steamapps folder into the main directory and finally the steamapps folder gets removed. Can you provide any logs, without them I really can‘t help.