-
Notifications
You must be signed in to change notification settings - Fork 40
Better error message in case of OpenVPN connection failure #241
Comments
Apparently, this error is a generic "Something went wrong with OpenVPN"-error, since a user where OpenVPN failed to connect due to timeout got the same error. |
The problem was a server clock issue, i.e. the server was not using NTP. As the Norwegian deploy(s) use two machines, it is very important that the time between those server is the same to avoid certificates being rejected as "not yet valid". In the new vpn-ca planned as a default for one of the next releases this is somewhat mitigated by issuing certificates that are valid starting 5 minutes in the past. |
It is difficult for the client to find out what went wrong, the server log usually has more details. Assuming the log is on... |
Getting the exact same error now for different issue. It seems the client really does use the wrong client cert or tls-crypt key. Not sure what is going on. It doesn't help the client doesn't log anything before the connection is successful :( |
Server log in this case:
|
My client suddenly failed asking me to verify that I am using the correct certificate. I as a technical user don't know whether I am using the correct certificate, the client should handle that for me. A less technical user wouldn't know either. The error should therefore be handled by the client.
In this case, clicking OK and trying again solved the problem for me, but I don't know if the client did anything in the background.
I noticed the string in the source code here:
macos/eduVPN/ConnectionService.swift
Line 85 in 4fea6a0
The text was updated successfully, but these errors were encountered: