ich777

Please read the first recommended post on top of this thread. Yes and no, answer is complicated, but if you are using something newer than Intel 10th gen this plugin won't do anything for you.

That should be possible but I'm not entirely sure how to do that, I will look that up and report back, I think there is somewhere a tutorial around here on the forums.

So I assume it is working now...?

I really don't know what this could be... Maybe 6.12.0 will solve that...

I don't understand, which container do you want to route through wg0? OpenVPN? Yes that's in theory possible but I wouldn't describe that as double protection...

Please remove the input ports, those are not necessary... Are you able to connect to the Deluge WebUI with 192.168.1.5:8112 if yes there should be no issue connection to Deluge. I completely missed that you haven't routed Radarr through the OpenVPN container, so localhost can't work.

Welchen Browser verwendest du denn? Du kannst das komplett umleiten auch aber du musst port 9666 vom container zum host im template auch freigeben. EDIT: Das funktioniert aber nur mit Click'n'Load...

Use localhost or 127.0.0.1 as the Hostname. BTW: You can also copy/paste pictures screenshots here on the forums.

Yes, but I don't recommend doing it like that since this can lead to hard crashes if not used properly.

As said, forget about what it displays in the Unraid GUI, just make sure that you've created a port mapping with the container port 8081 and the host mapping 8081 then you should be able to connect again when you are not routing it through the OpenVPN container. Anyways, I've tried this now with a test setup and have no issues connection to the OpenVPN container to the SABnzbd container on port 8081.

Wait, I completely missed that you've bound the card to VFIO or at least it seems that it's bound to VFIO but I didn't see any indication in the logs that the system itself bound it to VFIO, did you maybe do that manually? : 09:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) Subsystem: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:119e] Kernel driver in use: vfio-pci Kernel modules: nvidia_drm, nvidia 09:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio Controller [10de:10f0] (rev a1) Subsystem: NVIDIA Corporation GP104 High Definition Audio Controller [10de:119e] Taking a deeper look into it from what I can see you bind the card in your OPNSense VM (why?) : -device '{"driver":"vfio-pci","host":"0000:09:00.0","id":"hostdev0","bus":"pci.4","addr":"0x0"}'

Have you yet tried to set up a second instance on your server and see if does the same? I can't reproduce this on my server on a Fresh install and on my instance with ValheimPlus.

@Frostyfruit, see the comment from @Kilrah above.

Please wait for the next RC and try if it solves your issues.

At this point I have to ask: Are you really sure that you are using my container? Look at the differences in the logs... Mine even doesn't say anything about version 5.1.3.0 and I really don't know what this Prometheus message is all about... Do you maybe use any addons for the server?

Please update the container itself, this is now fixed.

This is normal since mono is used on Linux to run the .exe It seems that the container couldn't remove the Sonarr folder which lives in your directory for sonarr which is usually loacted in your appdata directory. Can you try to stop the container, go to your appdata directory and into the sonarr folder, there should be a folder called Sonarr, try to remove that Sonarr folder and start the container again. May I ask to what your appdata share is set in terms of Use Cache in the Share settings? Oh wait now that I've see it, do you use the nightly branch? If yes, give me a bit since I have to look into it if something has changed for version 4.x and I have to change the startup routine.

I really can't help with that since I've never saw that on my server, maybe try to create a post on the Sundtek forums or maybe @Sundtek can help over here. Did you try this adapter on your Vu+ for a few days or only for a few hours, maybe you are correct and the DVB-C/T USB device is faulty, it could as be the case that something doesn't play nicely with your hardware, maybe check if a settings for USB devices is suspicious or try another USB port on your motherboard

Ignore that please in the Unraid WebUI, where you still able to connect through 8080 to the container or did you have to use 8081? If you where still able to connect to it through 8080 then the container didn't save it. The container does nothing to change the port back to 8080 and I've tested it now over here and I'm able to change the port to 8081, are you sure you've clicked this button after changing the port:

It is really strange to me because the system log does show nothing, have you yet tried to boot into Unraid GUI mode and see if you get a output from your GPU? Maybe also try the legacy version 470.xx and reboot your server and see if this makes a difference.

Since you are running TShock I'm assuming you are using mods correct? Is it possible that a mod is causing this, I tried a fresh installed container from the CA App on my system.

Can you try to boot with Legacy Mode (CSM) and see if that makes a difference? I see nothing obvious. Also enable Above 4G Decoding or in your case it can be called like Support large PCIe Address Space or something with 64bit Address Space since HP and Dell calls these things always differently... What I can tell for sure these settings should be located in the PCI section from your BIOS.

Wait, there is something wrong, if you use SABnzbd on the bridge network, can you still connect through 8080 or do you have to use 8081?

Can you please try to not start the terminal in a maximized window? Maybe this will help... Does the container look also look like that? Another way to connect to the console is to open up a console window from Unraid and type in: 'docker exec -u terraria -ti [Name of your Container] screen -xS Terraria' (without quotes) to exit the screen session press CTRL+A and then CTRL+D or simply close the terminal window in the first place. This will basically do the same as my WebUI implementation.

Do you talk about that: No issue over here (I only typed in help because I don't know the commands but as you can see it is working) :