suRe

Oh, this is perfect. So all "bridged" dockers will route through vpn, and any "custom" docker network adapters, e.g. Container using ReverseProxy adapter will be reachable through normal ISP IP? Have not updated to RC Versions yet, so i can't test it on my own.

Hey, in your start post, it says "VPN tunneled access - In the future it may be possible to restrict it so that only specific Dockers use the VPN tunnel". Is there an ETA on that topic? I really want to tunnel my radarr/sabnzbd dockers through VPN 🙂

Yes, it works great in pretty much every country. But i got relatives living in egypt, and apparently egypt seems to be able to block the vpn traffic (started two weeks ago, before it worked perfect with udp 1194). I've read somewhere, that for example people living in china use TCP port 443 for VPN, since only on this port the VPN seem to be working. I hope it is more understandable now.

@SpaceInvaderOne Thank you for the updated Tutorial But how would one solve the following problem: I need to route the openVPN traffic through TCP port 443, otherwise i can't use openVPN. But i already have a letsencrypt docker configured as SpaceInvaderOne explained in his ReserveProxy/Nextcloud guide. So i'm basically forwarding TCP Port 443 -> 1443. How can i use this port with openVPN? What method are you using? A Wireguard docker would be awesome

So, i checked for power consumption without a cable plugged in - still the same. In the meantime i e-mailed AMD about this topic.

a) did not have to stub the video card. Is there a particular reason to do this? b) this i will have to try. I remember something of a "zero watt"-state with no cables plugged in. c) i tend to boot into no-gui mode (since i only have one gpu). this is where i first noticed the problem.

Just tested this, in BIOS and in GUI Mode the Power Consumption is the same, which is ridiculously too high. So, what does that mean? Any way to fix this?

As fas as i know, you can't install the newest AMD Relive Drivers on i440, only on Q35. The latest driver that worked on i440 without the driver crashing with a black screen is 18.2.1 (or 18.2.3?). Every driver after that has the same problem. Q35 just works out-of-the-box. Had the problem with a RX570 and a Vega56. Another user here in the forum had the same issue and changing to Q35 fixed this. (Ozon was his name as far as i remember).

Sounds like the exact same problem i'm having, although i got a Vega 56. Started a thread some time ago but didnt get an answer

Hey SpaceInvaderOne, i encountered the same problem as xanvincent. The problem is not Win10/Q35 related, since i am running a Win10 VM with Q35. If i use i440fx, i can't install the latest AMD Drivers (RX 570) without the driver getting stuck during installation (black screen), so i went with Q35 and everything works fine. In Linux on the other hand, i can't shut down any VM (also Q35) without having the "Unknown PCI header type '127'" error. Only a server reboot will fix this. There are several thread in this forum with this error, e.g.: https://forums.unraid.net/topic/75597-unknown-pci-header-type-error/?tab=comments#comment-696426&searchlight=1 https://forums.unraid.net/topic/71065-internal-error-unknown-pci-header-type-127-on-rx550/?tab=comments#comment-652514&searchlight=1 So, what might fix that?