UWonBiDVD

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About UWonBiDVD

  • Rank
    Newbie
  1. @Dyon YES YES YES!!!! root@5819c8e9fda4:/opt# curl ifconfig.me 131.255.4.108root@5819c8e9fda4 A new ovpn file fixed it! This is the VPN IP address, finally! Thank you for your help, that's helped me help myself and pick away at it. Still interested to know about the kill switch question I posted above, if you have the time to reply to it Now I need to learn how to save this so I don't have to paste the config in every time in SSH... that's my next task DVD
  2. OK, some progress. I found this article; https://www.synoforum.com/threads/device-dev-net-tun-not-working-anymore-after-docker-update-18-09-0-0513.3074/ and followed EVOTk's advice about downloading the TUN.sh file and executing it on my device. This now seems to allow the VPN to connect, and my logs look much healthier; 2020-12-11 09:43:11.525031 [INFO] Starting OpenVPN... Fri Dec 11 09:43:12 2020 WARNING: file 'credentials.conf' is group or others accessible Fri Dec 11 09:43:12 2020 OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKC
  3. Hmm, it looks as though other Synology users have had similar issues with this error. Maybe Synology isn't honouring the privileges command, it doesn't seem to create the folders for tun, or so other users seem to suggest. It looks like at a GUI level this could be fixed by ticking the box to execute with highest privileges, so I need to see what I can find to set in the docker run code to achieve the same thing.... One question I wanted to ask Dyon is around the kill switch. I can see the health check defaults to 5 minute intervals. Is that how often it checks for the kill switch
  4. Thanks, that's a good place for me to start looking. Another .ovpn file didn't help (tried UDP rather than TCP), and putting the credentials directly in the variables didn't help. I will see where my permissions / privileges are failing tomorrow. Thanks again, I will post back if I progress it or get stuck, maybe could help someone else you never know. Cheers DVD
  5. Thanks and I feel humbled you have updated it to be case insensitive haha, I will also have a look in more detail tomorrow. I found an invalid character in my password, I don't know why, it was copied and pasted from Nord VPN dashboard, anyway, get a different error now. I'll post it, but happy to work on it myself tomorrow. Will have a look at what you've shared above too, thanks! Oh yes, will also try using the VPN_USERNAME and PASSWORD variables as well. And try another VPN file seeing as I'm now a bit further Fri Dec 11 00:25:42 2020 VERIFY EKU OK Fri Dec 11 00:25:42 2020
  6. Oh my, what an embarrassing mistake! That's a lesson I won't forget... CaSe SeNsItIvE!!!! So, there is still an issue with the auth (right at the bottom), but I will look into it further; root@SYNOLOGY:~# docker logs pensive_kapitsa 2020-12-11 00:10:13.800848 [INFO] VPN_ENABLED defined as 'yes' 2020-12-11 00:10:13.857619 [INFO] DISABLE_IPV6 is set to '' 2020-12-11 00:10:13.913761 [INFO] Disabling IPv6 in sysctl 2020-12-11 00:10:13.977213 [INFO] VPN_TYPE defined as 'openvpn' 2020-12-11 00:10:14.066058 [WARNING] Unable to chown/chmod /config/open
  7. Thanks Dyon, that's really cool of you. Not sure what you can find in this... is there a better command I can run? I ran the command below, it sets a random name every time I delete and start it over again - interestingly, when I'm logged in as my own admin user and I type 'ID', it does show me that my UID=1026, so I'm not sure why it says PUID does not exist; root@SYNOLOGY:~# docker logs infallible_margulis 2020-12-10 23:50:40.121961 [INFO] VPN_ENABLED defined as 'YES' 2020-12-10 23:50:40.178897 [INFO] DISABLE_IPV6 is set to '' 2020-12-10 23:50:40.234163 [INFO] Dis
  8. Reverting back hasn't help, still shows my IP address. Am I meant to have the config and config/openvpn pointed to the container, rather than the Jackett application? Maybe I've made a huge fundamental mistake Thanks DVD
  9. That gave me a chuckle. You are right, that's exactly where I was looking - I didn't know there was a difference! 😂 Another lesson learnt 👍 I have run the above code and the IP is my real IP. I will dig a bit more, it's odd because I can't see where my config has gone wrong, hmmm. I will revert my container back to using the .ovpn file with the credentials.conf file, see if that makes a difference. Thanks for the reply, that was a really useful bit of info Thanks DVD
  10. Rather than keep editing my above post, I will add here. I have removed the user-auth-pass reference to credentials.conf in the .ovpn file, and changed the docker run command to the following to include the VPN credentials - still no VPN reference in the logs...; docker run --privileged -d \ -v /volume1/config/config2/:/config \ -v /volume1/downloads/downloads2/:/blackhole \ -e "VPN_ENABLED=YES" \ -e "VPN_TYPE=openvpn" \ -e "VPN_USERNAME=my_VPN_username" \ -e "VPN_PASSWORD=my_VPN_password" \ -e "LAN_NETWORK=192.168.1.0/24" \ -e "NAME_SERVERS
  11. Dyon, thanks for sharing your work on this. I'm a noob at Linux / Docker and all that jazz, but getting by, day by day. I tried to get this working in Synology using the GUI, but it was hard to tell whether it was correctly working. I've then gone back to basics and done it all from SSH into my Synology, and the container is running and there are no obvious errors in the Synology docker log, the Jackett web GUI is available via http://192.168.1.40:9117 (.40 is my NAS obviously) - I can add indexers no problem, but I've no idea whether the VPN is actually running. The logging shown in the Synol