Manually running server on Windows 7 error

Version: 4.1.17 OS: Windows 7, 64-bit Browser: Chrome 71

When I run the server manually and a new client connects, I see this error:

C:\Users\admin\Documents\openvpn-status-4.1.17>node server.js
(node:4628) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'C
lient ID' of undefined
    at clientToEntry (C:\Users\admin\Documents\openvpn-status-4.1.17\server.js:7
0:16)
    at client.on.cl (C:\Users\admin\Documents\openvpn-status-4.1.17\server.js:16
9:21)
    at emitOne (events.js:116:13)
    at client.emit (events.js:211:7)
    at getClients.then (C:\Users\admin\Documents\openvpn-status-4.1.17\openvpn.j
s:82:16)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
(node:4628) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). (rejection
 id: 1)
(node:4628) [DEP0018] DeprecationWarning: Unhandled promise rejections are depre
cated. In the future, promise rejections that are not handled will terminate the
 Node.js process with a non-zero exit code.

The new client does not show in the webpage. Note: this is the first time using the new management port instead of the connect/disconnect scripts in version 4.0.25.

[xinthose]

Everything works fine on Windows Server 2012 R2 and node 10.15.1 from master branch 7ceaa1de40b93cb248b1b64e3a85b5842d36807b

[xinthose]

OK. So the problem is that client is undefined but data is not. The problem is probably with string parsing then. I would imagine the OpenVPN management port is OS agnostic. Version 4.0.25 worked fine for me. I will see what I can do. Thank you for your help.