A certificate warning means the client cannot establish the expected trust for a secure connection. Causes can include an incorrect device clock, hostname mismatch or server certificate problem. Do not dismiss the warning by disabling verification.
Check the device clock
A substantially wrong date can make a valid certificate appear outside its validity period. Use the operating system's supported time settings and reconnect. This is especially relevant after a long period unplugged or a failed clock synchronisation.
Verify the supplied address
A certificate is issued for particular names. Replacing a hostname with a raw IP address or an invented alias can break that match. Use the provider's documented secure endpoint rather than modifying it to resemble another service.
Escalate persistent warnings
If time and address are correct, report the warning privately to the operator. Avoid sending passwords over a connection you cannot verify. A workaround that hides certificate errors removes a useful protection instead of repairing the trust problem.
