Ok, on chrome desktop there is no way to bypass the security

Yes, there is. I often have to use it to deal with some internal misconfigured site inside the corporate intranet (the cause is almost always that a certificate has expired, when it isn't it's because a host can be reached with two names and the cert matches only one of them, but that case can be fixed by using the proper URL). I have no trouble telling chrome desktop to bypass.

... and I always read the details before proceeding (finding out what chrome's problem with the cert is).

For some type of errors it is possible, for some other it isn't. Check the badssl website and test the various type of bad certs, you'll see.