Open VPN server on CHR trouble with 7.8

Hi, i have upgraded my CHR ovpn concentrator/dude server to the latest 7.8 from 7.7. It has 2 virtual cpu 1.699 Mhz and 4 giga of ram. I have 122 client connecting on it. When i have upgraded this at reboot i obtain cpu 100% on both cores and profiles show cpu consumption to 100% about ssl, i thing that a massive connect of all of my client saturated it. So i have created this firewall filter rule:
chain=input action=drop connection-state=!established protocol=tcp src-address-list=!Whitelist_ip dst-port=1194 log=no log-prefix=“”
If i disable this rule for some second and reactivating it i can reconnect all of my clients a little at a time. When all 122 client are connected the cpu load decerase from 100% to 5-20% and all working OK. But it seems that after some amount of time the problem appear again. I find the virtual machine rebooted (watchdog?) and cpu 100%. with 50% of clients connected. Is a know problem?

I had similar problems with version 7.7 too, but after having connected all the clients helping the server with that firewall rule the connections remained stable for months without ever dropping. From version 7.8 after some random time start to drop and both cpu become 100% saturated.
I’ve tried unencrypting some clients “none/[null-digest]” in an attempt to lighten the load but that doesn’t seem to make any difference. For now there is something that i can do for make my network working again?

7.7 saturate the cpu only on massive client reconnection, but accepting them a little at a time they work forever, cpu usage with all clients connected seems perfectly normal 5-20%.
7.8 saturate the cpu on massive client reconnection, accepting them a little at a time work for some hour, then randomly the cpu goes up to 100% anyway and drops me half of the clients or the CHR reboot itself.

There is a new voice in ovpn server “Key renegotiate sec” if i set to zero help a little bit but after several hour cpu 100% and same problem :frowning:.

Nothing, key renegotiation sec value doesnt change anything, after several hour the issue happen again.

Same here, downgrading to 7.7 work again.

Hi Meconiotronic

I have the very exact same problem
do you mean that downgrading to 7.7 and using the rule

chain=input action=drop connection-state=!established protocol=tcp src-address-list=!Whitelist_ip dst-port=1194 log=no log-prefix=“”

will work fine?

Anyone tested OVPN on 7.8 over UDP.
For case I experienced it seems OK over UDP, no more kernel crashes or high CPU load. See this. But we have HW router…

I experience exactly same issue (OVPN server, CHR, 7.11.2, 2x3GHz CPU, 1 GB RAM).
Each hour (default key renegotiation) I lose cca 50% of OVPN clients.

Anyone tried 7.12rc1? They mention “*) ovpn - improved system stability;”.

These issues with openvpn are chronic in version 7. I have an open support ticket addressing similar problems. I was able to stabilize the connections by making some changes. The first one was disabling “key renegotiate sec” by setting the value to 0 on the OpenVPN server. Then, I disabled renegotiation on the clients as well, using the “reneg-sec 0” option. Lastly, in the profile used on the OpenVPN server, in the “only one” option, I leave it marked as “no.” This way, I haven’t had any more issues.