ich777

You don't have to do anything other than install the plugin, everthying is handled by the plugin.

The xml files (tempaltes) are located in: /boot/config/plugins/dockerMan/templates-user/ Then you should be able to add them when you click on Add Container on the Docker page and select them from the drop down.

Yes, tested it myself and it doesn't work on the official one. You can easily switch between the containers by changing from ich777/jellyfin to jellyfin/jellyfin and vice versa.

Can you confirm that AMD VA-API is working properly in the official container? If yes, this container can be deprecated or better speaking switched over to the official one.

The "drivers" are included in the Kernel so you technically don't have to install anything. Maybe the next update from unRAID with a new Kernel version will solve the issue. Also radeontop only enables the driver and installs radeontop itself so you can see the usage from your GPU nothing more. But I really don't know if Frigate fully supports AMD iGPUs or better speaking APUs. Maybe it transcodes audio first and then starts to transcode video or vice versa...?

Maybe @binhex can help with that but I would recommend to make a post on the official support thread from the container since this is not related to the plugin. @alturismo can maybe also help, he uses Plex with TVHeadend and xteve if I'm not mistaken...

In this case no. But we can try something else next week if that's not too late for you. I will test it and get back to you.

This is really strange, I will try it on my test server with a fresh installed Prometheus Exporter, please give me some time since I'm currently on vacation.

No, do the following: Open up Steam Click on View Click on Server Click on Favorites Click on Add Server Enter: YOURunRAIDIP:27015 (also try YOURunRAIDIP:7777 that always depends on the game you are trying to connect to) Important Click on Refresh once more Then you should see the server and you can also connect through this window by double clicking on your server.

This may take a while to load the data in Grafana itself. Have you yet tried to restart unRAID itself? Do you have any other data sources in Grafana than Prometheus?

I'm not really the guy that can help with ARK but maybe @Cyd can help, I've seen a few people in this thread running a Cluster that consists of 6 containers. The second recommended post should help or am I wrong... at least the linked Github from @Cyd should shed some light on it. Don't know if anyone made a video on that, if not maybe @Sycotix can help with that...

Can you connect from a local browser to this URL? http://192.168.0.11:9617/metrics The reason might be that it tries to connect and it shows that it's actually connected but fails after a few seconds and if you refresh the page it shows the "real" status of the exporter. I think something might be wrong with the connection itself, please try if you can connect to the URL above. Adguard is on the host network and Prometheus and Grafana are on the "bridge" network, correct?

It could be an issue but I don't think so. What if you turn off HW transcoding in Frigate in general and only transcode with unmanic, does the same thing happen if yes, can you also turn on HW transcoding in Frigate and turn it off in unmanic? I think there could be an issue with one of the two applications and not with radeontop. HW transcoding will still work when it's at 100% but it should be a little slower than usual.

You have stubbed the card in your syslinux.config: BOOT_IMAGE=/bzimage pci-stub.ids=10de:1184 initrd=/bzroot ...and here you can see that it uses pci-stub instead of the nvidia module: 84:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:3774] Kernel driver in use: pci-stub Kernel modules: nvidia_drm, nvidia 84:00.1 Audio device [0403]: NVIDIA Corporation GK104 HDMI Audio Controller [10de:0e0a] (rev a1) Subsystem: eVga.com. Corp. GK104 HDMI Audio Controller [3842:3774] Please remove the part 'pci-stub.ids=10de:1184' and it should work fine (go to Main -> click on the blue text that says "Flash" -> remove the mentioned part -> click "Apply" -> "Reboot").

On the first page in the Troubleshooting section I've linked the Nvidia Unix Driver page where you can see which cards are supported by which driver (click on the driver version and on "Supported Products"). I don't think that a Tesla card is supported by this driver because these are Datacenter cards.

Have you changed anything to the container? On what unRAID version are you? Please upgrade at least to 6.9.2, seems like a strange error from SteamCMD. Please don't forward both TCP and UDP if only TCP or UDP is needed, some games doesn't like that and that is also from a security perspective bad... UDP Ports: 7777, 7778, 27015 TCP Port: 27020 (only if you need it, you don't necessarily have to forward this port) Please also check if you can see the server in the Steam Server Browser at Favorites -> click Add Server -> enter YOURunRAIDIP:27015

What? Why? Have you restarted the Docker Daemon once or even read the first post or the red warning about that you have to restart the Docker Daemon once? I think someone already forked my driver and also the repo and made it available, please ask in the Chinese language subforums.

Nein, nur ganzen controller und dann dort BluRay mittels SATA anschließen.

Does it work now?

I still can't reproduce this error. Have you tried since then to install the container, of course wipe it before completely: Delete the contianer Delete the l4d2 folder from your appdata directory Pull a fresh copy from the CA App On what unRAID version are you? Have you installed a Cache driver if yes, make sure that the appdata directory is set to use cache "Only" or "Prefer" in the Share settings. If you don't have a Cache drive make sure to point it at the right disk where your appdata directory is located and also make sure that the files aren't split over multiple directories. Also make sure to not set the game directory to a path like /mnt/user/appdata/... it always needs to know where the files are located physically, so to speak: /mnt/cache/appdata/... or /mnt/disk1/appdata/... Here is the log from a fresh pulled container from the CA App: l4d2.log

Then create it like that: Also make sure that you are on the latest version from the container first, maybe try to click on on the Docker page with Advanced View turned on.

Change this variable to 1.4.3.2 instead of 1.4.3.1:

That's really strange, I've tried it now also from the internet (connected my PC to the WiFi Hotspot from my phone) and it works flawlessly too...

So the plugin wasn't the issue and everything is now working I think?

Yes, looking good. This card can do h264 and h265 without a problem.