> Does anyone know potential causes of a device that can connect remote peers > via “http” but can’t connect to remote peers via “https”? e.g. can’t reach > https://mail.google.com/.., but can reach http://www.google.com, whereas > other devices can reach both sites. So it is not issue at remote peer, it > is the local device issue. I presume the difference in domain names is a typo, and you meant the same domain name for both. In any case, "can't connect" and "can't reach" aren't specific enough to do any problem determination. Is the problem one of these?: - Tries to connect to port 443, and the connection attempt times out. - Connects to port 443, and fails in attempting the TLS handshake. - Understands the TLS handshake, but doesn't accept the server's certificate. ...or is it something else? What, exactly, is the failure? Barry