-
[Support] alturismo - Repos
Cheers - nothing other than my own stupidity - will go and try this now and hopefully it then loads up!
-
[Support] alturismo - Repos
Thanks, that's what I thought so changed password etc but unfortunately still no luck. I take it the file should read username = 'my user' password = 'my password' In that format with the ' ' surrounding it, just want to check in not doing something stupid there?
-
[Support] alturismo - Repos
No worries thanks for taking the time to reply
-
ethan9482 joined the community
-
[Support] alturismo - Repos
Hi all Firstly, thank you so much for making the docker image, if I can get it to work it is exactly what I was after. Which leads me to my problem. I use NordVPN and I have put the ovpn file in the config folder and updated the logindata.conf also. It loads the file fine but just cycles through a login issue, the details are correct as far as I can see. To confirm the logindata.conf should read username = "email@address" password = password The output I am getting (in a loop) is below I am running a QNAP 251+, have xteve installed on another docker container and have it working fine, just keen to use your version and link it to NordVPN Any help appreciated! Cheers /config/uk1484.nordvpn.com.udp.ovpn exist /config/logindata.conf exist Mon May 11 12:56:00 2020 WARNING: file '/config/logindata.conf' is group or others accessible Mon May 11 12:56:00 2020 OpenVPN 2.4.7 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Mar 14 2019 Mon May 11 12:56:00 2020 library versions: OpenSSL 1.1.1d 10 Sep 2019, LZO 2.10 Mon May 11 12:56:00 2020 WARNING: --ping should normally be used with --ping-restart or --ping-exit Mon May 11 12:56:00 2020 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Mon May 11 12:56:00 2020 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Mon May 11 12:56:00 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]194.35.233.57:1194 Mon May 11 12:56:00 2020 Socket Buffers: R=[819200->819200] S=[819200->819200] Mon May 11 12:56:00 2020 UDP link local: (not bound) Mon May 11 12:56:00 2020 UDP link remote: [AF_INET]194.35.233.57:1194 Mon May 11 12:56:00 2020 TLS: Initial packet from [AF_INET]194.35.233.57:1194, sid=6c8c52be 50386772 Mon May 11 12:56:00 2020 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Mon May 11 12:56:00 2020 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA Mon May 11 12:56:00 2020 VERIFY OK: depth=1, C=PA, O=NordVPN, CN=NordVPN CA4 Mon May 11 12:56:00 2020 VERIFY KU OK Mon May 11 12:56:00 2020 Validating certificate extended key usage Mon May 11 12:56:00 2020 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Mon May 11 12:56:00 2020 VERIFY EKU OK Mon May 11 12:56:00 2020 VERIFY OK: depth=0, CN=uk1484.nordvpn.com Mon May 11 12:56:02 2020 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA Mon May 11 12:56:02 2020 [uk1484.nordvpn.com] Peer Connection Initiated with [AF_INET]194.35.233.57:1194 Mon May 11 12:56:03 2020 SENT CONTROL [uk1484.nordvpn.com]: 'PUSH_REQUEST' (status=1) Mon May 11 12:56:03 2020 AUTH: Received control message: AUTH_FAILED Mon May 11 12:56:03 2020 SIGTERM[soft,auth-failure] received, process exiting
ethan9482
Members
-
Joined
-
Last visited