ich777

On what Unraid version are you? What card do you want to get to run?

In the case for ACC you have to, otherwise the server won't work. ACC requires you to forward the ports otherwise it won't work and the server will loop. For most other server it's true what you are saying but not for ACC, the master server needs to connect to your server otherwise it won't work properly.

Please note that this is a dedicated server and not the client side. No, why? This is only the dedicated server and you need no HW acceleration, the game is not rendered. No. My containers are Load'n'Play, of course you have to forward the ports in the case for ACC otherwise the container, or better speaking the dedicated server will reboot constantly. You only have to forward the ports from the template with the appropriate protocol in your router.

But since you are using a Gigabyte board you are introducing most certainly other bugs...

Nothing yet. Please also make sure that the signal quality is decent. BTW the error from previously was not caused by the TV card whatsoever, it was caused by another device in your system but could cause also troubles for your TV card since the timings for those must be perfect. I really don't know what you could try, I just saw that you are using a Gigabyte board which are not the best in terms for BIOS support and have many bugs in them, at least that's my experience with them. Back then (Sandy Bridge) I've also had a Gigabyte board where I had stutters and issues like you've described after I switched to a ASUS board everything was running smoothly again <- I used DigitalDevices cards in that case. I can only recommend that you post an issue here with the exact description and with the syslog.txt, lscpci.txt, lscpu.txt and motherboard.txt from your Diagnostics. You can also try to move the card to a different PCIe slot and see if that makes a difference. Of course also make sure that you are on the latest BIOS version. Before that you could also try to enable/disable various settings from the PCIe sub menu in your BIOS and see if that makes a difference. Maybe someone over on GitHub knows how to solve that.

Please remember if you try the card in a different system woth a different OS that this is not saying much because what matters it the combination of the current hardware. You are the first who is reporting such an error for 6.11.5 and the driver doesn’t change for a Unraid version. I knew a few people who having none issues with this card/driver on 6.11.5 The only thing that I can recommend is that you create an Issue on GitHub from TBS. Do you made sure that you disabled power saving in TVHeadend?

Please append this to your syslinux.conf and reboot:

Please post your Diagnostics.

Did you change anything in the template? Please double check if you forwarded the ports with the correct protocol from the template (please don‘t forward other ports or add a protocol that isn‘t listed).

That is not possible and the container is not designed for that.

Thank you for the report, fixed for new installations.

Please post your Diagnostics. Did you reboot after unbinding the iGPU. Why did you bount it to VFIO in the first place anyways?

Remove the plugin, reboot, pull a fresh copy from the CA App, reboot again and see if it is working after you did that.

Of course, but you CPU simply can't keep up with the load from the audio transcoding and maybe subtitle processing.

As said above, this is most likely a bug in your BIOS. I also really can't tell if this is caused by the mobile T400 chip that your card is using, which is as said not officially supported by the driver from Nvidia.

Don‘t just change it. You have to change the confog so that the query port is 27016 and after that you have to delete the port entry with 27015 and create a new one with the host and container port set to 27016, of course you have to also use the correct protocol (UDP) in this case. No, how should I know that? I know bukkit/spigot but thats it. In the first post in this thread or every container that you have installed in the CA App.

No because I've given up on that currently, don't know if it would be working now but I don't think so. The server doesn't run reliably back then. EDIT: This is from Discord: So I'm not really interested in trying it again.

Then maybe think about changing the paths to the real file path since this will write directly to the disks and save some overhead and CPU cycles. It's just a recommendation from my side, you should be also fine if you are using the FUSE file path.

I do that in all my templates (or better speaking in almost all) by default, you can set it to /mnt/user/... if you want to but I don't recommend that because you can run into issues (mostly on my game server containers where they would simply segfault or simply not work <- this is caused because of the FUSE file path) and you save some overhead because you are not running it through FUSE but that is really negligible in the case for Edge. If you have your appdata set to use cache "Only" or "Prefer" nothing should go wrong (which it should be in my opinion) but if you've set it to "Yes" you should change the path to /mnt/user/... Hope that explains it a bit.

Exactly, wouldn't this work on Unraid if you mount for example the /mnt directory to it?

Done.

This is really strange since it is working for me and for @sonic6. Are you sure that you Docker image isn't corrupt or anything else? Do you have anything custom installed on your server through NerdTools?

On what Unraid version are you currently? 6.11.5?

My containers are all self maintained (or at least most of them) and I barely need to update them, however this is not the possible in all scenarios and this is where the issues start, EDGE works a bit different in that case. As said above I will look into that.

Maybe, but I have to look into this since I have to somehow get the version and keep the container up to date and other things that are a bit tricky on Chromium based browsers.