ich777

Can you please post screenshots from how you have your containers configured (Docker template screenshots) and which container do you want to route through the OpenVPN container? Are you using my container or which container are you using exactly? Can you also post screenshots, what do you want to route through and how it's configured? Are you using my container or which container are you using exactly?

Not that I‘m aware of… OSX or betrer speaking RealVNC should do that automatically.

A little bit more information would be helpful, please also post your Diagnostics. What is the output from sensors-detect from a terminal?

Oh just to let you know, I've implemented Pushbits notifications into Unraid which is a notification agent for Matrix-Synapse. Pushbits is based on the Gotify API and is working really well with Unraid. You can find the Docker container also in the CA App. & @kardinal EDIT: It looks something like that in the Unraid GUI: And if you click test you get this: The notifications are also color coded for Normal, Warning and Alert messages if enabled in Pushbits.

I have stopped creating containers for games that I don‘t own because giving support is impossible. However if you are willing to donate the game to me I‘m happy to look into it. I have only done a little bit of research but is there even a dedicated server available for this game?

This is nothing to worry about, skip the part with uninstalling and simplay reboot and install a fresh copy from the CA App.

Remove the Plugin through the GUI, reboot your server and grab a fresh copy from the CA App. This should do the trick. If you tried it multiple times please wait for at least an hour before you try this.

This is expected since you are telling your server to exclusively use it in VMs and so to speak Unraid can‘t talk to the card anymore because it‘s bound to VFIO. No, but there is a Prometheus plugin out there which you can use in combination with MSI Afterburner to export the metrics to Grafana for example and see the usage and so on.

Nope, tested and verified that it is working just fine. Just make sure that you just don't only forward the port to another port so to speak 9700 <-> 9701, you also have to change it in the config and delete the old port entry in the template and set the port to the same in terms of host and container port if you want to use another port. Forwarding ports to different port numbers doesn't work for most game servers. For a more in depth explanation look at the recommended posts on top for Valheim to run multiple servers, the only difference to Valheim is that you have to change the port in the config file <- please make sure to first stop the container before changing any config values! Some ISPs block ports by default, maybe your ISP is one of them. What does the log say? Usually it tells you if all the ports are open or not when the container is starting and it even tells you if a port is not working correctly.

Yes, there is no container available (at least for Linux) that works reliably with this dedicated server. I've tried multiple times to create a container for this game but it is not stable in any means and I won't release a container which isn't working as intended.

Exactly like @alturismo said, if the T400 isn’t enough look at a T600 or even at a T1000.

Please read the first recommended post on top of this thread. Anyways I think that this is not possible with the go client since they are using some kind of their own protocoll an top of VNC and even if you set a password in the container it won‘t change anything IIRC (a user a few years back had the same request and he switched to RealVNC). I think you can configure this but I really don‘t know how to do this since I don‘t own a MAC.

I think that go Connect uses another protocol or at least always requires a password. Please try another client like RealVNC, this should work fine IIRC. You just have to create a new port mapping in the template with the container port 5900 to host port 5900 (you can change the host port to whatever you want) then connect with: <UNRAIDIP>:<HOSTPORT>

But that doesn't mean it must work, it can work but must not if something is missing in the container or configured not properly. This means that the driver is just working fine in the container. I don't know because I'm not familiar with Agent-DVR, please troubleshoot this in the support thread from Agent-DVR.

Have you yet read the description from the variables in the template?

I don't think this is going to work. However I could compile the drivers but I think that needs to be fixed by Hauppauge. I would ask Hauppauge if it is even supported on Linux and why that it doesn't load properly. I really don't know how to do that, maybe try to ask the support. My recommendation is always to use Digital Devices or Sundtek Tuners.

But your provider (NordVPN) changed something: https://github.com/ich777/docker-openvpn-client/issues/10#issuecomment-1614093879

Have you yet tried card=59? I know it's a different card but it has the exact same chip as your combo card for DVB-S TBH I really don't like these Hauppauge cards... They can get pretty complicated fast... Is there maybe a firmware update for the card available? I can't imagine that this is how it should work.

I think he was referring to this because you have wrote twice NVIDIA_VISIBLE_DEVICES Are you sure that the container even support Nvidia HW acceleration? I don't know this container but I would recommend that you post in the support thread from that container. If you open up a container console (not a Unraid Terminal) and issue: nvidia-smi Do you get the same output? If yes the driver is working correctly and it is most likely that something in the container is missing so that Nvidia is not supported or something inside the application is not configured properly.

I'm currently on vacation but support first... I see one thing here: Jun 30 16:50:25 servermonkey3 kernel: m88ds3103 0-0069: Unknown device. Chip_id=71 I think this chip is responsible for DVB-S in your case since it's a DVB-S chip: Click Have you also seen my previous post about removing the modifications in your go file?

This should be a combination from two cards I think, I'll have to investigate further, anyways always pass through the main device directory /dev/dvb and never /dev/dvb/adapterN because this will over complicate things. I will report back ASAP, have to look into this. EDIT: Because I've saw it, please remove your entry from the go file and instead add this line to your syslinux.config: cx23885.card=52 This is a bit more user friendly. Should look something like that:

Did you also added the device /dev/dvb in the container template (please note that I mean as device and not as path). Have you done that already?

Please post your Diagnostics so that I can look into this more in depth. Where do you want to use the card? Plex, TVHeadend?

No, this is not the reason why it is not working. You can ignore that message because it's caused by steamcmd and when the dedicated server starts steamcmd isn't running anymore. I can only tell you that I got multiple people who are running the latest version without an issue. Please also read one post above your post.

This is most likel not the case, the driver for the iGPUs on Linux are all In Tree drivers which you usually can‘t revert back to another driver. Intel GPU TOP is only a visualisazion for your iGPU and not a driver. Is h265 working for example in Jellyfin? Usually this is something that needs to be solved in the container because the Intel Media Driver is too old or not compatible, at least this was the case back in the day where I built Jellyfin in my own.