Opened 4 years ago
Closed 2 years ago
#1386 closed Bug / Defect ( wontfix )
"Errors occurred" popup gives invalid logfile path
| Reported by: | MrScottAtt | Owned by: | OpenVPN Inc. |
|---|---|---|---|
| Priority: | trivial | Milestone: | |
| Component: | Generic / unclassified | Version: | OpenVPN Connect for Windows |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | log |
| Cc: |
Description
On Windows 10 Pro, OpenVPN popped up "Errors occurred" with message:
"See the logfile 'C:\Program Files (x86)\OpenVPN Technologies\OpenVPN Client\core\ovpntray.exe.log' for details"
On examining that path, I find ovpntray.exe and ovpntray.dll, but no .exe.log files. The only .log file found is at:
C:\Program Files (x86)\OpenVPN Technologies\OpenVPN Client\etc\log\capi.log
Either the logfile path is incorrect, or the logfile did not get created.
Note: this may be the wrong place for this ticket? However if there's a bug in the commercial version, I'd expect it to be in the Community version as well.
Note: in the system tray it says "OpenVPN 2.7.1.111" which does not appear in the Version: pulldown.
Change History (3)
comment:1 Changed 4 years ago by
| Owner: | set to OpenVPN Inc. |
|---|---|
| Status: | new → assigned |
comment:2 Changed 4 years ago by
comment:3 Changed 2 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
OpenVPN Inc does not want to receive any feedback for the "Connect"
OpenVPN clients via the community bug trackers (here and in GH issues).
Please resubmit - if still relevant - via
https://support.openvpn.net/
Indeed this is the wrong place to post bugs about the commercial version - but the colleagues will take care of it :-)
The community version today uses a totally different code base which shares pretty much nothing but the protocol specification. Windows Connect is based on OpenVPN 3, which was a complete rewrite.