I'm having a hard time getting the OpenVPN logs. This is the only thing that I'm getting in server.log:

09-18-2025 18:14:34.206 DEBUG [monitor-device-inform-pool-1] [] c.t.s.o.m.d.m.d.p.o.OsgPoeUtilizationHandler(): handlePoeUtilizationInform osgInformBody {"needReply":0,"vpn":{"ipSecs":[],"tuns":[],"openvpn":[{"id":410256073,"userId":1067656855,"userName":"rebeca","infa":1,"localIp":"10.0.200.1","remoteIp":"10.0.200.6","downP":232706,"down":21146731,"upP":254491,"up":139560041,"uptime":8797,"dns":"10.0.200.1, 8.8.8.8"},{"id":410256073,"userId":235042181,"userName":"oana","infa":1,"localIp":"10.0.200.1","remoteIp":"10.0.200.10","downP":75770,"down":6735360,"upP":85344,"up":53215655,"uptime":3336,"dns":"10.0.200.1, 8.8.8.8"}]}}
09-18-2025 18:14:34.207 DEBUG [monitor-device-inform-pool-0] [] c.t.s.o.m.d.m.i.v.VpnStatsInformHandler(): vpn tunnel list size: 0
09-18-2025 18:14:34.207 DEBUG [monitor-device-inform-pool-0] [] c.t.s.o.m.c.l.MonitorLiteCbcService(): <LITE CBC> omadacId fa5217a20cf9c15325575caee1e53255, Category false
09-18-2025 18:14:34.207 DEBUG [manage-inform-work-group-2] [] c.t.s.c.l.m.ReadWriteLockServiceMemImpl(): [lockService]get ReadWriteLock lockName:module:manager:device, businessId:omadac.id:fa5217a20cf9c15325575caee1e53255:device.mac:EC-75-0C-D2-A7-5C

nothing relating to handshake. Where are you getting the logs from?

  @laurentiu907 , from standalone - System Tools - System Log.  Or, syslog server will show the same information if configured.  

Yeah unfortunately mine is linked to a cloud controller - no standalone access and the stuff that comes out from the controller is scarce in details.

It's now stable for about 5 hours. :))))

DST is set and updating just fine.

  @Ethan-TP after uprgading to this beta i cant connect to my er605 openvpn server

connection timeout

add.

where s wan???

even local connect to my er605 192.168.6.1  fails

  @laurentiu907 I have a V2.0 version with the latest firmware, 2.3.0 Build 20250428 Rel.18967. I think i have updated already because of this problem... 

I could change the port but i will have some work to access the remote workers and change the configuration file on each one. And it seems that it would be a temporary fix...

This is how the uptime looks like (without this beta firmware which I'm afraid to try in production) from what I've read above.

  @YuriyB Are you saying you cannot set the WAN and IP pool or that the beta firmware wiped out those settings?  You'll probably have to re-set that and then if the handshake still does not work, re-export the certificate and update the OpenVPN client with it.  Please let me know how that goes so I know what to do when I try this ;)  

Also, why TCP instead of UDP on your config? 

  @drac8029 

1. after update and first restart for a few minutes process "openssl dhparam -out" take high cpu usage so i think this beta rebuild ovpn certificate??

2.  yes, after update firmware wiped out that setting.

3. new ovpn server and export new certificate it began to work.

and rolled back to official 2.3.0 Build 20250428 Rel.18967 because didnt find any changes.

habit to use tcp on ovpn and udp on wireguard :)))

Both controllers are now solid for 13 hours each - so this is not confirmed as a fix.

I'm assuming that all others affected are good at least for 13 hours (without user intervention).

Right?