[ViX_Misc] OpenVPN 'Enter Auth Username' error

[bbbuk]

Hi All,

I'm using 5.4.008 and just tried using OpenVPN and getting following error from log:-

Thu Mar 18 15:02:54 2021 us=951985   auth_user_pass_file = 'stdin'
Thu Mar 18 15:02:54 2021 us=952017 OpenVPN 2.4.3 arm-oe-linux-gnueabi [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov  3 2020
Thu Mar 18 15:02:54 2021 us=952070 library versions: OpenSSL 1.0.2r  26 Feb 2019, LZO 2.10
Thu Mar 18 15:02:54 2021 us=952149 neither stdin nor stderr are a tty device and you have neither a controlling tty nor systemd - can't ask for 'Enter Auth Username:'.  If you used --daemon, you need to use --askpass to make passphrase-protected keys work, and you can not use --auth-nocache.
Thu Mar 18 15:02:54 2021 us=952182 Exiting due to fatal error

The client.conf file hasn't changed last time I used OpenVPN (few weeks ago). I tried downloading latest openvpn config file from my VPN (PIA) and still same error.

This error is on Vu+ Duo 4K SE and my old Solo2 so it's not compiling error.

I downloaded OpenVPN client for my laptop and used same config file and no issues which leads me could something have changed recently to cause this issue?

Github OE-A OpenVPN source files haven't changed recently.

My first thought is it an error to how E2 allows input of username and password? Windows version you get a prompt but with E2 you have to use following line in client.conf:-

auth-user-pass /etc/openvpn/pass.file

Has anyone who updated in last week or so having issues now and are they also using PIA ?

Thanks

 

[lincsat]

I've just upgraded a ZGemma H7 to 5.4.008 and PIA connects fine. The only warnings are about usernames may be saved in cache and IPv6 fails. It connects with IPv4 as expected.

I do setup the conf slightly differently and don't use the path to the password file. I use

auth-user-pass password.txt

Let me know if you want to try my config file

 

[bbbuk]

Thanks @lincsat, it's now working.

Removing the path and renaming password file to what you have resolved it. That path has been in there for sometime so something must have changed that prevents openvpn from parsing path. I wouldnt expect the filename being the underlying cause.

Anyhow, thanks :thumbsup: