Monitor considered up whenever TCP succeeds yet TLS fails

📑 I have found these related issues/pull requests I have been unable to find related issues and/or pull requests. 🛡️ Security Policy • I have read and agree to Uptime Kuma's [Security Policy]( 📝 Description As the title says. I have a setup where I am proxying a service that uses TLS. The TCP connection to the proxy succeeds, and I have then configured uptime-kuma to attempt a TLS handshake. The handshake fails, because the remote immediately disconnects, since the backend of the proxy is down. However, the monitor is still up: <img width="612" height="89" alt="Image" src=" /> 👟 Reproduction steps 1. Start some sort of TCP server (netcat?) that immediately disconnects after the first data packet is sent. Alternatively, use some sort of TCP proxy service that points to nothing 2. Add a monitor to uptime-kuma for this faulty TCP server 3. Observe the message "TLS connection failed", yet the monitor is up 👀 Expected …