apefray

@Dyon Just wanted to revisit this..... Unfortunately, after several weeks of working with Windscribe to get this working, I had the thought of using a different VPN docker. Im now using the OPENVPN-Client Docker and hey presto it all now works as it should. I am now able to connect to emby through both 4G and Broadband. Not sure why your app isn't working with Broadband connections though (for me at least) but Emby is now fully functional through a 4G router and CGNAT.

Hi Dyon, Tried it with an incognito window, still the same...... The router is running at about 76mbps download and 32mbps upload as tested on the router.....

@Dyon Ok, everything appears to be working as it should be: DelugeVPN is now using Windscribe and is working passthroughvpn is working with Emby being passed through it Can access Emby both on the Lan and Wan as intended, except, the Wan side only works when using mobile broadband on a phone. For some strange reason, trying to access Emby from outside the Lan using standard home broadband doesn't work as it should. When connecting to Emby over the Internet, it's very slow, and doesn't load fully. If it does manage to load and present the login screen, after entering the login credentials, nothing happens, it just sits at the login screen, checking the Emby dashboard shows a connection though. However, accessing Emby over 4G from a phone or a laptop/computer using the personal hotspot on the phone, everything works as it should. So why can I access Emby using Mobile Broadband, but not using standard home broadband (tried using BT, Virgin, Sky..... All produce the same issue)

@Dyon Yahhhhh, we have success. So easy through windscibe compared to PIA....... Im now running Emby through the passthroughvpn app and can access it through the LAN and WAN The only small issue I seem to have (although it maybe nothing), In the logs it shows the following warnings: Sun Jun 6 11:04:22 2021 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1602', remote='link-mtu 1550' Sun Jun 6 11:04:22 2021 WARNING: 'cipher' is used inconsistently, local='cipher AES-256-CBC', remote='cipher AES-256-GCM' Sun Jun 6 11:04:22 2021 WARNING: 'auth' is used inconsistently, local='auth SHA512', remote='auth [null-digest]' Are these anything to worry about? I checked the Windscribe-StaticIP.ovpn file and it shows the following settings: auth SHA512 cipher AES-256-CBC So why does the server differ??? Next, to get delugeVPN to work with windscribe

Well, I haven't been too impressed with PIA lately, so maybe its time to change anyway. I have just read a few documents on Windscribe, and it appears I can do exactly what I want to do quite easily, with most of the settings in my account Happy Days........

Or I suppose I could just sign up to Windscribe and follow your tutorial, lol! That maybe the easy option, assuming doing this will work as I intend?

@Dyon I have installed the passthroughvpn app, and have it connecting to PIA. Through the app I am running Emby, however, I am unable to access Emby from outside the network. The reason for using your passthroughvpn app is that I use a 4G Router for my internet connection, and of course, they use CGNAT so anything that I want to access outside my network doesn't work through the internet connection, in this example, I want to connect to Emby from outside my LAN. As I say, I have a OPENVPN connection using your app, and it appears to be runnning, and Emby is now pointing at the passthroughvpn app. I can access and use Emby within my LAN, but I believe I need to do a PIA portforward to open Emby up to the internet. Your instructions mention using a Windscribe Static IP, but I assume I can do the same with port forwarding through the PIA OPENVPN Connection? I have read through the PIA Portforwarding posts on the PIA forum, and they suggest using the following script: PIA Portforward How would I insert/use this script to enable the Portforward using your app??? Anyone else tried doing this?? Any suggestions?? Cheers

I too would like my VM to access the Internet through my OVPN-Client Container. Unfortunatley @tinyaim your solution deals with Dockers being routed through another Docker, what we are talking about is ensuring our VM uses the OVPN-Client Container to access the internet.

Hi, I installed the NO-IP docker yesterday afternoon, filled in the details inf the config file, NO-IP then created the no-ip2.generated file and everything appears to be working. When I first started the Docker it then updated my NO-IP account with the IP address I am running on, but it appears it hasn't updated since. I logged into my NO-IP account, went to the manage hostname page, and clicked on the info icon and its showing last updated 22 hours ago i.e. when I first started the Docker. It hasn't updated since. I have checked the Docker log and cannot see any problems and I see this being generated every min: Process 18, started as noip2-x86_64 -c /config/no-ip2.generated.conf, (version 2.1.9)Using configuration from /config/no-ip2.generated.confLast IP Address set ***************Account ***************configured for:***************Updating every 30 minutes via /dev/eth0 with NAT enabled. The Last IP address set is my correct IP address, the Account shows the correct email address, and the configured for show the correct hostname. Am I missing something?