It was imported by WinBox successful (i.e. it did not report any errors). Nevertheless, 30 seconds (timeout?) after enabling the interface I see error:
terminating... - TLS error: handshake timed out (6)
The same config works great on Linux OVPN client on my laptop (especially tested it) so one can rule out an issue on the server’s side.
In other words, I rely on certificate/private_key+password for authentication and encryption. I am not absolutely sure but I hope to be safe enough. In my case, although I tried to make it work with cert+pass**+tls**, it didn’t worked no matter how much I tried, so I had to use only cert/key+pass.
As I understood, tls is just a supplementary layer of security (it seems that was recently added but not fully functional). Tls-auth strengthens the pre-authentication and negotiation phase, but encryption based on the cert/key+pass hope to be safe enough anyway. Please note that only key/cert won’t work since mikrotik asks for cert**+pass** for security reasons.
You can disable tls in order to make it work and have a starting point. At least you will know what part of the config causes the error. You can then try to add tls and try to make it work with tls also.
Maybe an update will fix this in the near future.