There was a regression introduced w/ Merlin 386.1, where the certificates were issued using SHA1 for signing, when it should have been SHA256. It would cause these types of warning messages. But AFAIK, this was corrected by 386.4 and beyond.
However, what happened to some ppl is as they upgraded to 386.4 and beyond, they reused the old certificates rather than let the newer firmware generate new certificates based on SHA256. It wasn't a problem until newer software on other platforms updated as well and finally started rejecting SHA1.
The way to correct it, of course, is to let the router regenerate your certs.
You can verify the signing of your server certificates on the router w/ the following commands.
Code:
openssl x509 -noout -text -in /jffs/openvpn/vpn_crt_server1_ca
openssl x509 -noout -text -in /jffs/openvpn/vpn_crt_server1_crt
openssl x509 -noout -text -in /jffs/openvpn/vpn_crt_server1_client_crt
openssl x509 -noout -text -in /jffs/openvpn/vpn_crt_server2_ca
openssl x509 -noout -text -in /jffs/openvpn/vpn_crt_server2_crt
openssl x509 -noout -text -in /jffs/openvpn/vpn_crt_server2_client_crt
If all else fails, you can always manage and generate your own certs, keys, etc., using EasyRSA, then configure them as you please. In fact, some ppl do for other reasons (e.g., to get around the fact the router only generates *one* client certificate to be shared by all users).