ich777

But then your iGPU doesn't work or am I wrong? Do you have a monitor or a dummy dongle connected?

Wouldn't it be better to make the Docker work again, don't know if the plugin is actively maintained anymore.

Wait, the default way is to use in a Docker container not in the plugin, have you passed over the path /dev/dvb to the container?

I really don't understand what you mean, does it work properly? It uses a USB tuner because of this (this is a snippet from your syslog): mc: Linux media interface: v0.10 dw2102: su3000_identify_state dvb-usb: found a 'TeVii S482 (tuner 1)' in warm state. dw2102: su3000_power_ctrl: 1, initialized 0 dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. dvbdev: DVB: registering new adapter (TeVii S482 (tuner 1)) usb 1-1: media controller created dvb-usb: MAC address: 00:18:bd:5b:be:23 dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered. This card actually has a USB hub on it and uses USB tuners: Click You should be able to use it in TVHeadend, or what is the exact issue here?

Please also include your Diagnostics. Is anything not working?

Unbalance kann das, schöne GUI und perfektes Plugin.

Transcend 32GB USB 2.0 kann ich empfehlen. Findest nahezu überall.

@062bel313 & @lovingHDTV I've now forked the OpenVPN container, rebased it to Debian Bullseye and pushed it to DockerHub. You only have to switch the Repository from 'dperson/openvpn-client' to 'ich777/openvpn-client' and maybe add '--sysctl net.ipv6.conf.all.disable_ipv6=0' (without quotes) to the Extra Parameters (you have to turn on the 'Advanced View' to see the 'Extra Parameters') if you don't use/need IPv6 like in this screenshot:

Please try to boot with Legacy mode instead of UEFI mode and make sure that you've enable "Above 4G Decoding" and "Resizable BAR Support" in your BIOS (maybe you got only the "Above 4G Decoding" option). Here is the error that the plugin reports and is most likely related to Above 4G Decoding beeing disabled: nvidia-nvlink: Nvlink Core is being initialized, major device number 245 NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR3 is 0M @ 0x0 (PCI:0000:06:00.0) nvidia: probe of 0000:06:00.0 failed with error -1 NVRM: The NVIDIA probe routine failed for 1 device(s). NVRM: None of the NVIDIA devices were initialized. nvidia-nvlink: Unregistered the Nvlink Core, major device number 245 nvidia-nvlink: Nvlink Core is being initialized, major device number 245 NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR3 is 0M @ 0x0 (PCI:0000:06:00.0) nvidia: probe of 0000:06:00.0 failed with error -1 NVRM: The NVIDIA probe routine failed for 1 device(s). NVRM: None of the NVIDIA devices were initialized. nvidia-nvlink: Unregistered the Nvlink Core, major device number 245

Do you have other services exposed to the internet without a VPN or just this cluster? Maybe your ISP uses a hidden NAT, that would explain why it doesn't work.

With GVT-g you don't pass through the real iGPU you pass through a virtual iGPU and that is done by the plugin when you start a VM.

Maybe there is a safety timeout that the WebUI is logging you out, that's my best guess. But it shouldn't be related to the port change that you've done in the template from port 8080 to 8081.

Sorry no, that won't work, completely forgot that DirSyncPro was on a different VNC server version... Now everything is fixed. Please do the following: Go to the Docker page and enable Advanced View Click on to update the container to the latest version Turn off the Advanced View on the Docker page (letting it turned on actually produces load on your server) Since you've set the variable already inside the container template and you've set the password it should work after you've updated the container.

Please don't set your graphics card like that, please read the second post on how to use GVT-g

Have you restarted your server after you've pressed Download or am I wrong?

Actually not, only the plugin page but not the driver is installed, have you tried to click the "Download" button on the driver page itself yet? What card are you using? Can you try to switch to the latest production version and then click the Download button? If that also doesn't work can you try if this download is working for you: Click Have you installed AdGuard, PiHole or any other blocking software in your network, maybe try to disable it when downloading the driver.

This should also work but I'm really not that familiar with 11th Gen, on 10th Gen it works just fine. I've heard that if you boot with legacy that your iGPU is disabled, but I'm not really sure if that's actually the case.

Do you need this parameter in your syslinux.conf: i915.alpha_support=1 if not, please remove it and report back please.

Can you post your Diagnostics please? It says that the driver package was found locally, are you updating the package or how did you get to this window?

Doesn't he mean the boot mode itself? CSM (Legacy) or UEFI and that he had switch over to CSM? I don't think so, never tried that, because such a container also would need to run as privileged because this container then needs control over the full system.

Sorry, but I really can't help here since I've never had set up an ARK cluster or even played ARK long enough to know what you are talking about...

This isn't possible from what I know. One thing that I could imagine is that you don't bind the card to VFIO (the GPU should work in the VM anyways without being bound to VFIO with the newer Nvidia drivers) install the Nvidia Driver plugin and always launch nvidia-persistenced with a hook when the VM is off and kill it when the VM is started. If you do that you are making sure that the card goes to P8 (lowest idle power state) when the VM is off. But first I would recommend that you check if the card is working without the VFIO binding. I think the easier way is to install the Nvidia Driver plugin and create the hook files for the VM.

No, if you log in through the Docker console you are root, by typing in "su $USER" you are changing to the real user for the application itself so that it creates the file where it should be. Tested it now on my own, you are completely correct, doesn't work when the directory doesn't exist, have changed the post to create the directory first, thank you for the heads up. To be honest, I don't built any functionality into this container so that the application can run as root for security reasons (very few of my container have this ability to run as root eg: Krusader, luckyBackup).

Yes, don't do that, because when you use it in bridge mode you don't have the LAN IP in your Docker container available and it can't listen on that IP, you always should use 0.0.0.0 in the Container if possible. Glad to hear that it is now working.

Can you please tell me the exact steps/commands that you've done? Do you run DirSyncPro as root?