Chrome and your server could not agree on how to encrypt the connection. On a small business site this almost always means there is no certificate for that exact name, not that ciphers are wrong.
yoursite.com and www.yoursite.com. Often one works and the other has no certificate. Add the missing name to the certificate.shop.yoursite.com is covered, dev.shop.yoursite.com is not.openssl s_client -connect yoursite.com:443 -tls1_2. If that fails, ask the host to enable TLS 1.2 and 1.3.If none of these fit, send me the address and I will check which names and protocols your server offers.
Want the rest of your site checked after it is back? Run a free 40-point check at tinkeraudit.com.