On Fri, 04 Jun 2021 20:55:40 +0000, tincantech via Openvpn-users <openvpn-users@lists.sourceforge.net> wrote:
>Down to business: > >If your client cannot connect to your server then you MUST read the server log >to: > >* See if the client tried to connect to the server. > Your server log will have details. > >* See what errors are logged in the server log. > No errors are logged in the client log because Openvpn server is too secure > to give away details to the client. > >If your server log does not have any record concerning the client connection >attempt >then your client has failed to "find" your server. Of course it has, I have already written about the TLS errors... > > REPEAT post since my previous attempt was blocked due to excessive size... Now I have performed the following: - Stopped the VPN services on the test server - Made sure that verb 4 is in effect in the server conf file - Changed logging from log-append to just log so old stuff is erased - Started the tunnel-only service on the test server at 00:24:10 Next on the RPI client: - verified that verb 4 is in the client conf file - Connected successfully to the server (at 00:25:53) Then on the Windows 10 client: - verified verb 4 also here - Started a connection attempt at 00:27:03 - Noted that (as expected) the connection failed, showing TLS error after 60s - Disconnected the client connection attempts at 00:28:30 Finally on the RPi client: - Disconnected (using Ctrl-C in the terminal) VPN at 00:29:00 - Retrieved the client log file Then retrieved the logs as follows (long post...): ----- Now trying to attach compressed logfiles rather than adding the text right here... -- Bo Berglund Developer in Sweden _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
