Ошибка 112 net err no ssl versions enabled

// Copyright (c) 2012 The Chromium Authors. All rights reserved. // Use of this source code is governed by a BSD-style license that can be // found in the LICENSE file. // This file intentionally does not have header guards, it’s included // inside a macro to generate enum. // This file contains the list of network errors. // // Ranges: // 0- 99 System related errors // 100-199 Connection related errors // 200-299 Certificate errors // 300-399 HTTP errors // 400-499 Cache errors // 500-599 ? // 600-699 FTP errors // 700-799 Certificate manager errors // 800-899 DNS resolver errors // An asynchronous IO operation is not yet complete. This usually does not // indicate a fatal error. Typically this error will be generated as a // notification to wait for some external notification that the IO operation // finally completed. NET_ERROR(IO_PENDING, —1) // A generic failure occurred. NET_ERROR(FAILED, —2) // An operation was aborted (due to user action). NET_ERROR(ABORTED, —3) // An argument to the function is incorrect. NET_ERROR(INVALID_ARGUMENT, —4) // The handle or file descriptor is invalid. NET_ERROR(INVALID_HANDLE, —5) // The file or directory cannot be found. NET_ERROR(FILE_NOT_FOUND, —6) // An operation timed out. NET_ERROR(TIMED_OUT, —7) // The file is too large. NET_ERROR(FILE_TOO_BIG, —8) // An unexpected error. This may be caused by a programming mistake or an // invalid assumption. NET_ERROR(UNEXPECTED, —9) // Permission to access a resource, other than the network, was denied. NET_ERROR(ACCESS_DENIED, —10) // The operation failed because of unimplemented functionality. NET_ERROR(NOT_IMPLEMENTED, —11) // There were not enough resources to complete the operation. NET_ERROR(INSUFFICIENT_RESOURCES, —12) // Memory allocation failed. NET_ERROR(OUT_OF_MEMORY, —13) // The file upload failed because the file’s modification time was different // from the expectation. NET_ERROR(UPLOAD_FILE_CHANGED, —14) // The socket is not connected. NET_ERROR(SOCKET_NOT_CONNECTED, —15) // The file already exists. NET_ERROR(FILE_EXISTS, —16) // The path or file name is too long. NET_ERROR(FILE_PATH_TOO_LONG, —17) // Not enough room left on the disk. NET_ERROR(FILE_NO_SPACE, —18) // The file has a virus. NET_ERROR(FILE_VIRUS_INFECTED, —19) // The client chose to block the request. NET_ERROR(BLOCKED_BY_CLIENT, —20) // A connection was closed (corresponding to a TCP FIN). NET_ERROR(CONNECTION_CLOSED, —100) // A connection was reset (corresponding to a TCP RST). NET_ERROR(CONNECTION_RESET, —101) // A connection attempt was refused. NET_ERROR(CONNECTION_REFUSED, —102) // A connection timed out as a result of not receiving an ACK for data sent. // This can include a FIN packet that did not get ACK’d. NET_ERROR(CONNECTION_ABORTED, —103) // A connection attempt failed. NET_ERROR(CONNECTION_FAILED, —104) // The host name could not be resolved. NET_ERROR(NAME_NOT_RESOLVED, —105) // The Internet connection has been lost. NET_ERROR(INTERNET_DISCONNECTED, —106) // An SSL protocol error occurred. NET_ERROR(SSL_PROTOCOL_ERROR, —107) // The IP address or port number is invalid (e.g., cannot connect to the IP // address 0 or the port 0). NET_ERROR(ADDRESS_INVALID, —108) // The IP address is unreachable. This usually means that there is no route to // the specified host or network. NET_ERROR(ADDRESS_UNREACHABLE, —109) // The server requested a client certificate for SSL client authentication. NET_ERROR(SSL_CLIENT_AUTH_CERT_NEEDED, —110) // A tunnel connection through the proxy could not be established. NET_ERROR(TUNNEL_CONNECTION_FAILED, —111) // No SSL protocol versions are enabled. NET_ERROR(NO_SSL_VERSIONS_ENABLED, —112) // The client and server don’t support a common SSL protocol version or // cipher suite. NET_ERROR(SSL_VERSION_OR_CIPHER_MISMATCH, —113) // The server requested a renegotiation (rehandshake). NET_ERROR(SSL_RENEGOTIATION_REQUESTED, —114) // The proxy requested authentication (for tunnel establishment) with an // unsupported method. NET_ERROR(PROXY_AUTH_UNSUPPORTED, —115) // During SSL renegotiation (rehandshake), the server sent a certificate with // an error. // // Note: this error is not in the -2xx range so that it won’t be handled as a // certificate error. NET_ERROR(CERT_ERROR_IN_SSL_RENEGOTIATION, —116) // The SSL handshake failed because of a bad or missing client certificate. NET_ERROR(BAD_SSL_CLIENT_AUTH_CERT, —117) // A connection attempt timed out. NET_ERROR(CONNECTION_TIMED_OUT, —118) // There are too many pending DNS resolves, so a request in the queue was // aborted. NET_ERROR(HOST_RESOLVER_QUEUE_TOO_LARGE, —119) // Failed establishing a connection to the SOCKS proxy server for a target host. NET_ERROR(SOCKS_CONNECTION_FAILED, —120) // The SOCKS proxy server failed establishing connection to the target host // because that host is unreachable. NET_ERROR(SOCKS_CONNECTION_HOST_UNREACHABLE, —121) // The request to negotiate an alternate protocol failed. NET_ERROR(NPN_NEGOTIATION_FAILED, —122) // The peer sent an SSL no_renegotiation alert message. NET_ERROR(SSL_NO_RENEGOTIATION, —123) // Winsock sometimes reports more data written than passed. This is probably // due to a broken LSP. NET_ERROR(WINSOCK_UNEXPECTED_WRITTEN_BYTES, —124) // An SSL peer sent us a fatal decompression_failure alert. This typically // occurs when a peer selects DEFLATE compression in the mistaken belief that // it supports it. NET_ERROR(SSL_DECOMPRESSION_FAILURE_ALERT, —125) // An SSL peer sent us a fatal bad_record_mac alert. This has been observed // from servers with buggy DEFLATE support. NET_ERROR(SSL_BAD_RECORD_MAC_ALERT, —126) // The proxy requested authentication (for tunnel establishment). NET_ERROR(PROXY_AUTH_REQUESTED, —127) // A known TLS strict server didn’t offer the renegotiation extension. NET_ERROR(SSL_UNSAFE_NEGOTIATION, —128) // The SSL server attempted to use a weak ephemeral Diffie-Hellman key. NET_ERROR(SSL_WEAK_SERVER_EPHEMERAL_DH_KEY, —129) // Could not create a connection to the proxy server. An error occurred // either in resolving its name, or in connecting a socket to it. // Note that this does NOT include failures during the actual «CONNECT» method // of an HTTP proxy. NET_ERROR(PROXY_CONNECTION_FAILED, —130) // A mandatory proxy configuration could not be used. Currently this means // that a mandatory PAC script could not be fetched, parsed or executed. NET_ERROR(MANDATORY_PROXY_CONFIGURATION_FAILED, —131) // We detected an ESET product intercepting our HTTPS connections. Since these // products are False Start intolerant, we return this error so that we can // give the user a helpful error message rather than have the connection hang. NET_ERROR(ESET_ANTI_VIRUS_SSL_INTERCEPTION, —132) // We’ve hit the max socket limit for the socket pool while preconnecting. We // don’t bother trying to preconnect more sockets. NET_ERROR(PRECONNECT_MAX_SOCKET_LIMIT, —133) // The permission to use the SSL client certificate’s private key was denied. NET_ERROR(SSL_CLIENT_AUTH_PRIVATE_KEY_ACCESS_DENIED, —134) // The SSL client certificate has no private key. NET_ERROR(SSL_CLIENT_AUTH_CERT_NO_PRIVATE_KEY, —135) // The certificate presented by the HTTPS Proxy was invalid. NET_ERROR(PROXY_CERTIFICATE_INVALID, —136) // An error occurred when trying to do a name resolution (DNS). NET_ERROR(NAME_RESOLUTION_FAILED, —137) // Permission to access the network was denied. This is used to distinguish // errors that were most likely caused by a firewall from other access denied // errors. See also ERR_ACCESS_DENIED. NET_ERROR(NETWORK_ACCESS_DENIED, —138) // The request throttler module cancelled this request to avoid DDOS. NET_ERROR(TEMPORARILY_THROTTLED, —139) // A request to create an SSL tunnel connection through the HTTPS proxy // received a non-200 (OK) and non-407 (Proxy Auth) response. The response // body might include a description of why the request failed. NET_ERROR(HTTPS_PROXY_TUNNEL_RESPONSE, —140) // We were unable to sign the CertificateVerify data of an SSL client auth // handshake with the client certificate’s private key. // // Possible causes for this include the user implicitly or explicitly // denying access to the private key, the private key may not be valid for // signing, the key may be relying on a cached handle which is no longer // valid, or the CSP won’t allow arbitrary data to be signed. NET_ERROR(SSL_CLIENT_AUTH_SIGNATURE_FAILED, —141) // The message was too large for the transport. (for example a UDP message // which exceeds size threshold). NET_ERROR(MSG_TOO_BIG, —142) // Error cdoe -143 available. // Violation of limits (e.g. imposed to prevent DoS). NET_ERROR(LIMIT_VIOLATION, —144) // WebSocket protocol error occurred. NET_ERROR(WS_PROTOCOL_ERROR, —145) // Connection was aborted for switching to another ptotocol. // WebSocket abort SocketStream connection when alternate protocol is found. NET_ERROR(PROTOCOL_SWITCHED, —146) // Returned when attempting to bind an address that is already in use. NET_ERROR(ADDRESS_IN_USE, —147) // An operation failed because the SSL handshake has not completed. NET_ERROR(SSL_HANDSHAKE_NOT_COMPLETED, —148) // SSL peer’s public key is invalid. NET_ERROR(SSL_BAD_PEER_PUBLIC_KEY, —149) // The certificate didn’t match the built-in public key pins for the host name. // The pins are set in net/base/transport_security_state.cc and require that // one of a set of public keys exist on the path from the leaf to the root. NET_ERROR(SSL_PINNED_KEY_NOT_IN_CERT_CHAIN, —150) // Server request for client certificate did not contain any types we support. NET_ERROR(CLIENT_AUTH_CERT_TYPE_UNSUPPORTED, —151) // Server requested one type of cert, then requested a different type while the // first was still being generated. NET_ERROR(ORIGIN_BOUND_CERT_GENERATION_TYPE_MISMATCH, —152) // Certificate error codes // // The values of certificate error codes must be consecutive. // The server responded with a certificate whose common name did not match // the host name. This could mean: // // 1. An attacker has redirected our traffic to his server and is // presenting a certificate for which he knows the private key. // // 2. The server is misconfigured and responding with the wrong cert. // // 3. The user is on a wireless network and is being redirected to the // network’s login page. // // 4. The OS has used a DNS search suffix and the server doesn’t have // a certificate for the abbreviated name in the address bar. // NET_ERROR(CERT_COMMON_NAME_INVALID, —200) // The server responded with a certificate that, by our clock, appears to // either not yet be valid or to have expired. This could mean: // // 1. An attacker is presenting an old certificate for which he has // managed to obtain the private key. // // 2. The server is misconfigured and is not presenting a valid cert. // // 3. Our clock is wrong. // NET_ERROR(CERT_DATE_INVALID, —201) // The server responded with a certificate that is signed by an authority // we don’t trust. The could mean: // // 1. An attacker has substituted the real certificate for a cert that // contains his public key and is signed by his cousin. // // 2. The server operator has a legitimate certificate from a CA we don’t // know about, but should trust. // // 3. The server is presenting a self-signed certificate, providing no // defense against active attackers (but foiling passive attackers). // NET_ERROR(CERT_AUTHORITY_INVALID, —202) // The server responded with a certificate that contains errors. // This error is not recoverable. // // MSDN describes this error as follows: // «The SSL certificate contains errors.» // NOTE: It’s unclear how this differs from ERR_CERT_INVALID. For consistency, // use that code instead of this one from now on. // NET_ERROR(CERT_CONTAINS_ERRORS, —203) // The certificate has no mechanism for determining if it is revoked. In // effect, this certificate cannot be revoked. NET_ERROR(CERT_NO_REVOCATION_MECHANISM, —204) // Revocation information for the security certificate for this site is not // available. This could mean: // // 1. An attacker has compromised the private key in the certificate and is // blocking our attempt to find out that the cert was revoked. // // 2. The certificate is unrevoked, but the revocation server is busy or // unavailable. // NET_ERROR(CERT_UNABLE_TO_CHECK_REVOCATION, —205) // The server responded with a certificate has been revoked. // We have the capability to ignore this error, but it is probably not the // thing to do. NET_ERROR(CERT_REVOKED, —206) // The server responded with a certificate that is invalid. // This error is not recoverable. // // MSDN describes this error as follows: // «The SSL certificate is invalid.» // NET_ERROR(CERT_INVALID, —207) // The server responded with a certificate that is signed using a weak // signature algorithm. NET_ERROR(CERT_WEAK_SIGNATURE_ALGORITHM, —208) // The domain has CERT records which are tagged as being an exclusive list of // valid fingerprints. But the certificate presented was not in this list. NET_ERROR(CERT_NOT_IN_DNS, —209) // The host name specified in the certificate is not unique. NET_ERROR(CERT_NON_UNIQUE_NAME, —210) // The server responded with a certificate that contains a weak key (e.g. // a too-small RSA key). NET_ERROR(CERT_WEAK_KEY, —211) // Add new certificate error codes here. // // Update the value of CERT_END whenever you add a new certificate error // code. // The value immediately past the last certificate error code. NET_ERROR(CERT_END, —212) // The URL is invalid. NET_ERROR(INVALID_URL, —300) // The scheme of the URL is disallowed. NET_ERROR(DISALLOWED_URL_SCHEME, —301) // The scheme of the URL is unknown. NET_ERROR(UNKNOWN_URL_SCHEME, —302) // Attempting to load an URL resulted in too many redirects. NET_ERROR(TOO_MANY_REDIRECTS, —310) // Attempting to load an URL resulted in an unsafe redirect (e.g., a redirect // to file:// is considered unsafe). NET_ERROR(UNSAFE_REDIRECT, —311) // Attempting to load an URL with an unsafe port number. These are port // numbers that correspond to services, which are not robust to spurious input // that may be constructed as a result of an allowed web construct (e.g., HTTP // looks a lot like SMTP, so form submission to port 25 is denied). NET_ERROR(UNSAFE_PORT, —312) // The server’s response was invalid. NET_ERROR(INVALID_RESPONSE, —320) // Error in chunked transfer encoding. NET_ERROR(INVALID_CHUNKED_ENCODING, —321) // The server did not support the request method. NET_ERROR(METHOD_NOT_SUPPORTED, —322) // The response was 407 (Proxy Authentication Required), yet we did not send // the request to a proxy. NET_ERROR(UNEXPECTED_PROXY_AUTH, —323) // The server closed the connection without sending any data. NET_ERROR(EMPTY_RESPONSE, —324) // The headers section of the response is too large. NET_ERROR(RESPONSE_HEADERS_TOO_BIG, —325) // The PAC requested by HTTP did not have a valid status code (non-200). NET_ERROR(PAC_STATUS_NOT_OK, —326) // The evaluation of the PAC script failed. NET_ERROR(PAC_SCRIPT_FAILED, —327) // The response was 416 (Requested range not satisfiable) and the server cannot // satisfy the range requested. NET_ERROR(REQUEST_RANGE_NOT_SATISFIABLE, —328) // The identity used for authentication is invalid. NET_ERROR(MALFORMED_IDENTITY, —329) // Content decoding of the response body failed. NET_ERROR(CONTENT_DECODING_FAILED, —330) // An operation could not be completed because all network IO // is suspended. NET_ERROR(NETWORK_IO_SUSPENDED, —331) // FLIP data received without receiving a SYN_REPLY on the stream. NET_ERROR(SYN_REPLY_NOT_RECEIVED, —332) // Converting the response to target encoding failed. NET_ERROR(ENCODING_CONVERSION_FAILED, —333) // The server sent an FTP directory listing in a format we do not understand. NET_ERROR(UNRECOGNIZED_FTP_DIRECTORY_LISTING_FORMAT, —334) // Attempted use of an unknown SPDY stream id. NET_ERROR(INVALID_SPDY_STREAM, —335) // There are no supported proxies in the provided list. NET_ERROR(NO_SUPPORTED_PROXIES, —336) // There is a SPDY protocol framing error. NET_ERROR(SPDY_PROTOCOL_ERROR, —337) // Credentials could not be established during HTTP Authentication. NET_ERROR(INVALID_AUTH_CREDENTIALS, —338) // An HTTP Authentication scheme was tried which is not supported on this // machine. NET_ERROR(UNSUPPORTED_AUTH_SCHEME, —339) // Detecting the encoding of the response failed. NET_ERROR(ENCODING_DETECTION_FAILED, —340) // (GSSAPI) No Kerberos credentials were available during HTTP Authentication. NET_ERROR(MISSING_AUTH_CREDENTIALS, —341) // An unexpected, but documented, SSPI or GSSAPI status code was returned. NET_ERROR(UNEXPECTED_SECURITY_LIBRARY_STATUS, —342) // The environment was not set up correctly for authentication (for // example, no KDC could be found or the principal is unknown. NET_ERROR(MISCONFIGURED_AUTH_ENVIRONMENT, —343) // An undocumented SSPI or GSSAPI status code was returned. NET_ERROR(UNDOCUMENTED_SECURITY_LIBRARY_STATUS, —344) // The HTTP response was too big to drain. NET_ERROR(RESPONSE_BODY_TOO_BIG_TO_DRAIN, —345) // The HTTP response contained multiple distinct Content-Length headers. NET_ERROR(RESPONSE_HEADERS_MULTIPLE_CONTENT_LENGTH, —346) // SPDY Headers have been received, but not all of them — status or version // headers are missing, so we’re expecting additional frames to complete them. NET_ERROR(INCOMPLETE_SPDY_HEADERS, —347) // No PAC URL configuration could be retrieved from DHCP. This can indicate // either a failure to retrieve the DHCP configuration, or that there was no // PAC URL configured in DHCP. NET_ERROR(PAC_NOT_IN_DHCP, —348) // The HTTP response contained multiple Content-Disposition headers. NET_ERROR(RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION, —349) // The HTTP response contained multiple Location headers. NET_ERROR(RESPONSE_HEADERS_MULTIPLE_LOCATION, —350) // SPDY server refused the stream. Client should retry. This should never be a // user-visible error. NET_ERROR(SPDY_SERVER_REFUSED_STREAM, —351) // SPDY server didn’t respond to the PING message. NET_ERROR(SPDY_PING_FAILED, —352) // The request couldn’t be completed on an HTTP pipeline. Client should retry. NET_ERROR(PIPELINE_EVICTION, —353) // The HTTP response body transferred fewer bytes than were advertised by the // Content-Length header when the connection is closed. NET_ERROR(CONTENT_LENGTH_MISMATCH, —354) // The HTTP response body is transferred with Chunked-Encoding, but the // terminating zero-length chunk was never sent when the connection is closed. NET_ERROR(INCOMPLETE_CHUNKED_ENCODING, —355) // The cache does not have the requested entry. NET_ERROR(CACHE_MISS, —400) // Unable to read from the disk cache. NET_ERROR(CACHE_READ_FAILURE, —401) // Unable to write to the disk cache. NET_ERROR(CACHE_WRITE_FAILURE, —402) // The operation is not supported for this entry. NET_ERROR(CACHE_OPERATION_NOT_SUPPORTED, —403) // The disk cache is unable to open this entry. NET_ERROR(CACHE_OPEN_FAILURE, —404) // The disk cache is unable to create this entry. NET_ERROR(CACHE_CREATE_FAILURE, —405) // Multiple transactions are racing to create disk cache entries. This is an // internal error returned from the HttpCache to the HttpCacheTransaction that // tells the transaction to restart the entry-creation logic because the state // of the cache has changed. NET_ERROR(CACHE_RACE, —406) // The server’s response was insecure (e.g. there was a cert error). NET_ERROR(INSECURE_RESPONSE, —501) // The server responded to a <keygen> with a generated client cert that we // don’t have the matching private key for. NET_ERROR(NO_PRIVATE_KEY_FOR_CERT, —502) // An error adding to the OS certificate database (e.g. OS X Keychain). NET_ERROR(ADD_USER_CERT_FAILED, —503) // *** Code -600 is reserved (was FTP_PASV_COMMAND_FAILED). *** // A generic error for failed FTP control connection command. // If possible, please use or add a more specific error code. NET_ERROR(FTP_FAILED, —601) // The server cannot fulfill the request at this point. This is a temporary // error. // FTP response code 421. NET_ERROR(FTP_SERVICE_UNAVAILABLE, —602) // The server has aborted the transfer. // FTP response code 426. NET_ERROR(FTP_TRANSFER_ABORTED, —603) // The file is busy, or some other temporary error condition on opening // the file. // FTP response code 450. NET_ERROR(FTP_FILE_BUSY, —604) // Server rejected our command because of syntax errors. // FTP response codes 500, 501. NET_ERROR(FTP_SYNTAX_ERROR, —605) // Server does not support the command we issued. // FTP response codes 502, 504. NET_ERROR(FTP_COMMAND_NOT_SUPPORTED, —606) // Server rejected our command because we didn’t issue the commands in right // order. // FTP response code 503. NET_ERROR(FTP_BAD_COMMAND_SEQUENCE, —607) // PKCS #12 import failed due to incorrect password. NET_ERROR(PKCS12_IMPORT_BAD_PASSWORD, —701) // PKCS #12 import failed due to other error. NET_ERROR(PKCS12_IMPORT_FAILED, —702) // CA import failed — not a CA cert. NET_ERROR(IMPORT_CA_CERT_NOT_CA, —703) // Import failed — certificate already exists in database. // Note it’s a little weird this is an error but reimporting a PKCS12 is ok // (no-op). That’s how Mozilla does it, though. NET_ERROR(IMPORT_CERT_ALREADY_EXISTS, —704) // CA import failed due to some other error. NET_ERROR(IMPORT_CA_CERT_FAILED, —705) // Server certificate import failed due to some internal error. NET_ERROR(IMPORT_SERVER_CERT_FAILED, —706) // PKCS #12 import failed due to invalid MAC. NET_ERROR(PKCS12_IMPORT_INVALID_MAC, —707) // PKCS #12 import failed due to invalid/corrupt file. NET_ERROR(PKCS12_IMPORT_INVALID_FILE, —708) // PKCS #12 import failed due to unsupported features. NET_ERROR(PKCS12_IMPORT_UNSUPPORTED, —709) // Key generation failed. NET_ERROR(KEY_GENERATION_FAILED, —710) // Server-bound certificate generation failed. NET_ERROR(ORIGIN_BOUND_CERT_GENERATION_FAILED, —711) // Failure to export private key. NET_ERROR(PRIVATE_KEY_EXPORT_FAILED, —712) // DNS error codes. // DNS resolver received a malformed response. NET_ERROR(DNS_MALFORMED_RESPONSE, —800) // DNS server requires TCP NET_ERROR(DNS_SERVER_REQUIRES_TCP, —801) // DNS server failed. This error is returned for all of the following // error conditions: // 1 — Format error — The name server was unable to interpret the query. // 2 — Server failure — The name server was unable to process this query // due to a problem with the name server. // 4 — Not Implemented — The name server does not support the requested // kind of query. // 5 — Refused — The name server refuses to perform the specified // operation for policy reasons. NET_ERROR(DNS_SERVER_FAILED, —802) // DNS transaction timed out. NET_ERROR(DNS_TIMED_OUT, —803) // The entry was not found in cache, for cache-only lookups. NET_ERROR(DNS_CACHE_MISS, —804)

A complete list of Google Chrome Errors you may receive while browsing a website. Let us know if you receive an error list below — including details of how you received the error and any other information to help solve fixing it. You can copy/paste the error from this list when you post below.

* Use the comment form below to let us know about your Google Chrome error and relevant details so we can help you solve it. *

«ERR_ABORTED»:-3,
«ERR_ACCESS_DENIED»:-10,
«ERR_ADDRESS_INVALID»:-108,
«ERR_ADDRESS_IN_USE»:-147,
«ERR_ADDRESS_UNREACHABLE»:-109,
«ERR_ADD_USER_CERT_FAILED»:-503,
«ERR_ALPN_NEGOTIATION_FAILED»:-122,
«ERR_BAD_SSL_CLIENT_AUTH_CERT»:-117,
«ERR_BLOCKED_BY_ADMINISTRATOR»:-22,
«ERR_BLOCKED_BY_CLIENT»:-20,
«ERR_BLOCKED_BY_RESPONSE»:-27,
«ERR_BLOCKED_ENROLLMENT_CHECK_PENDING»:-24,
«ERR_CACHE_AUTH_FAILURE_AFTER_READ»:-410,
«ERR_CACHE_CHECKSUM_MISMATCH»:-408,
«ERR_CACHE_CHECKSUM_READ_FAILURE»:-407,
«ERR_CACHE_CREATE_FAILURE»:-405,
«ERR_CACHE_LOCK_TIMEOUT»:-409,
«ERR_CACHE_MISS»:-400,
«ERR_CACHE_OPEN_FAILURE»:-404,
«ERR_CACHE_OPERATION_NOT_SUPPORTED»:-403,
«ERR_CACHE_RACE»:-406,
«ERR_CACHE_READ_FAILURE»:-401,
«ERR_CACHE_WRITE_FAILURE»:-402,
«ERR_CERTIFICATE_TRANSPARENCY_REQUIRED»:-214,
«ERR_CERT_AUTHORITY_INVALID»:-202,
«ERR_CERT_COMMON_NAME_INVALID»:-200,
«ERR_CERT_CONTAINS_ERRORS»:-203,
«ERR_CERT_DATABASE_CHANGED»:-714,
«ERR_CERT_DATE_INVALID»:-201,
«ERR_CERT_END»:-215,
«ERR_CERT_ERROR_IN_SSL_RENEGOTIATION»:-116,
«ERR_CERT_INVALID»:-207,
«ERR_CERT_NAME_CONSTRAINT_VIOLATION»:-212,
«ERR_CERT_NON_UNIQUE_NAME»:-210,
«ERR_CERT_NO_REVOCATION_MECHANISM»:-204,
«ERR_CERT_REVOKED»:-206,
«ERR_CERT_UNABLE_TO_CHECK_REVOCATION»:-205,
«ERR_CERT_VALIDITY_TOO_LONG»:-213,
«ERR_CERT_WEAK_KEY»:-211,
«ERR_CERT_WEAK_SIGNATURE_ALGORITHM»:-208,

«ERR_CLIENT_AUTH_CERT_TYPE_UNSUPPORTED»:-151,
«ERR_CONNECTION_ABORTED»:-103,
«ERR_CONNECTION_CLOSED»:-100,
«ERR_CONNECTION_FAILED»:-104,
«ERR_CONNECTION_REFUSED»:-102,
«ERR_CONNECTION_RESET»:-101,
«ERR_CONNECTION_TIMED_OUT»:-118,
«ERR_CONTENT_DECODING_FAILED»:-330,
«ERR_CONTENT_DECODING_INIT_FAILED»:-371,
«ERR_CONTENT_LENGTH_MISMATCH»:-354,
«ERR_CONTEXT_SHUT_DOWN»:-26,
«ERR_CT_CONSISTENCY_PROOF_PARSING_FAILED»:-171,
«ERR_CT_NO_SCTS_VERIFIED_OK»:-158,
«ERR_CT_STH_INCOMPLETE»:-169,
«ERR_CT_STH_PARSING_FAILED»:-168,
«ERR_DISALLOWED_URL_SCHEME»:-301,
«ERR_DNS_CACHE_MISS»:-804,
«ERR_DNS_MALFORMED_RESPONSE»:-800,
«ERR_DNS_SEARCH_EMPTY»:-805,
«ERR_DNS_SERVER_FAILED»:-802,
«ERR_DNS_SERVER_REQUIRES_TCP»:-801,
«ERR_DNS_SORT_ERROR»:-806,
«ERR_DNS_TIMED_OUT»:-803,
«ERR_EMPTY_RESPONSE»:-324,
«ERR_ENCODING_CONVERSION_FAILED»:-333,
«ERR_ENCODING_DETECTION_FAILED»:-340,
«ERR_FAILED»:-2,
«ERR_FILE_EXISTS»:-16,
«ERR_FILE_NOT_FOUND»:-6,
«ERR_FILE_NO_SPACE»:-18,
«ERR_FILE_PATH_TOO_LONG»:-17,
«ERR_FILE_TOO_BIG»:-8,
«ERR_FILE_VIRUS_INFECTED»:-19,
«ERR_FTP_BAD_COMMAND_SEQUENCE»:-607,
«ERR_FTP_COMMAND_NOT_SUPPORTED»:-606,
«ERR_FTP_FAILED»:-601,
«ERR_FTP_FILE_BUSY»:-604,
«ERR_FTP_SERVICE_UNAVAILABLE»:-602,
«ERR_FTP_SYNTAX_ERROR»:-605,
«ERR_FTP_TRANSFER_ABORTED»:-603,
«ERR_HOST_RESOLVER_QUEUE_TOO_LARGE»:-119,
«ERR_HTTPS_PROXY_TUNNEL_RESPONSE»:-140,
«ERR_HTTP_1_1_REQUIRED»:-365,
«ERR_ICANN_NAME_COLLISION»:-166,
«ERR_IMPORT_CA_CERT_FAILED»:-705,
«ERR_IMPORT_CA_CERT_NOT_CA»:-703,
«ERR_IMPORT_CERT_ALREADY_EXISTS»:-704,
«ERR_IMPORT_SERVER_CERT_FAILED»:-706,
«ERR_INCOMPLETE_CHUNKED_ENCODING»:-355,
«ERR_INCOMPLETE_SPDY_HEADERS»:-347,
«ERR_INSECURE_RESPONSE»:-501,
«ERR_INSUFFICIENT_RESOURCES»:-12,
«ERR_INTERNET_DISCONNECTED»:-106,
«ERR_INVALID_ARGUMENT»:-4,
«ERR_INVALID_AUTH_CREDENTIALS»:-338,
«ERR_INVALID_CHUNKED_ENCODING»:-321,
«ERR_INVALID_HANDLE»:-5,
«ERR_INVALID_HTTP_RESPONSE»:-370,
«ERR_INVALID_RESPONSE»:-320,
«ERR_INVALID_SPDY_STREAM»:-335,
«ERR_INVALID_URL»:-300,
«ERR_IO_PENDING»:-1,
«ERR_KEY_GENERATION_FAILED»:-710,
«ERR_MALFORMED_IDENTITY»:-329,
«ERR_MANDATORY_PROXY_CONFIGURATION_FAILED»:-131,
«ERR_METHOD_NOT_SUPPORTED»:-322,
«ERR_MISCONFIGURED_AUTH_ENVIRONMENT»:-343,
«ERR_MISSING_AUTH_CREDENTIALS»:-341,
«ERR_MSG_TOO_BIG»:-142,
«ERR_NAME_NOT_RESOLVED»:-105,
«ERR_NAME_RESOLUTION_FAILED»:-137,
«ERR_NETWORK_ACCESS_DENIED»:-138,
«ERR_NETWORK_CHANGED»:-21,
«ERR_NETWORK_IO_SUSPENDED»:-331,
«ERR_NOT_IMPLEMENTED»:-11,
«ERR_NO_PRIVATE_KEY_FOR_CERT»:-502,
«ERR_NO_SSL_VERSIONS_ENABLED»:-112,
«ERR_NO_SUPPORTED_PROXIES»:-336,
«ERR_ORIGIN_BOUND_CERT_GENERATION_TYPE_MISMATCH»:-152,
«ERR_OUT_OF_MEMORY»:-13,
«ERR_PAC_NOT_IN_DHCP»:-348,
«ERR_PAC_SCRIPT_FAILED»:-327,
«ERR_PAC_SCRIPT_TERMINATED»:-367,
«ERR_PAC_STATUS_NOT_OK»:-326,
«ERR_PKCS12_IMPORT_BAD_PASSWORD»:-701,
«ERR_PKCS12_IMPORT_FAILED»:-702,
«ERR_PKCS12_IMPORT_INVALID_FILE»:-708,
«ERR_PKCS12_IMPORT_INVALID_MAC»:-707,
«ERR_PKCS12_IMPORT_UNSUPPORTED»:-709,
«ERR_PRECONNECT_MAX_SOCKET_LIMIT»:-133,
«ERR_PRIVATE_KEY_EXPORT_FAILED»:-712,
«ERR_PROXY_AUTH_REQUESTED»:-127,
«ERR_PROXY_AUTH_REQUESTED_WITH_NO_CONNECTION»:-364,
«ERR_PROXY_AUTH_UNSUPPORTED»:-115,
«ERR_PROXY_CERTIFICATE_INVALID»:-136,
«ERR_PROXY_CONNECTION_FAILED»:-130,
«ERR_PROXY_HTTP_1_1_REQUIRED»:-366,
«ERR_QUIC_HANDSHAKE_FAILED»:-358,
«ERR_QUIC_PROTOCOL_ERROR»:-356,
«ERR_REQUEST_RANGE_NOT_SATISFIABLE»:-328,
«ERR_RESPONSE_BODY_TOO_BIG_TO_DRAIN»:-345,
«ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION»:-349,
«ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_LENGTH»:-346,
«ERR_RESPONSE_HEADERS_MULTIPLE_LOCATION»:-350,
«ERR_RESPONSE_HEADERS_TOO_BIG»:-325,
«ERR_RESPONSE_HEADERS_TRUNCATED»:-357,
«ERR_SELF_SIGNED_CERT_GENERATION_FAILED»:-713,
«ERR_SOCKET_IS_CONNECTED»:-23,
«ERR_SOCKET_NOT_CONNECTED»:-15,
«ERR_SOCKET_RECEIVE_BUFFER_SIZE_UNCHANGEABLE»:-162,
«ERR_SOCKET_SEND_BUFFER_SIZE_UNCHANGEABLE»:-163,
«ERR_SOCKET_SET_RECEIVE_BUFFER_SIZE_ERROR»:-160,
«ERR_SOCKET_SET_SEND_BUFFER_SIZE_ERROR»:-161,
«ERR_SOCKS_CONNECTION_FAILED»:-120,
«ERR_SOCKS_CONNECTION_HOST_UNREACHABLE»:-121,
«ERR_SPDY_COMPRESSION_ERROR»:-363,
«ERR_SPDY_FLOW_CONTROL_ERROR»:-361,
«ERR_SPDY_FRAME_SIZE_ERROR»:-362,
«ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY»:-360,
«ERR_SPDY_PING_FAILED»:-352,
«ERR_SPDY_PROTOCOL_ERROR»:-337,
«ERR_SPDY_RST_STREAM_NO_ERROR_RECEIVED»:-372,
«ERR_SPDY_SERVER_REFUSED_STREAM»:-351,
«ERR_SPDY_SESSION_ALREADY_EXISTS»:-143,
«ERR_SSL_BAD_PEER_PUBLIC_KEY»:-149,
«ERR_SSL_BAD_RECORD_MAC_ALERT»:-126,
«ERR_SSL_CLIENT_AUTH_CERT_BAD_FORMAT»:-164,
«ERR_SSL_CLIENT_AUTH_CERT_NEEDED»:-110,
«ERR_SSL_CLIENT_AUTH_CERT_NO_PRIVATE_KEY»:-135,
«ERR_SSL_CLIENT_AUTH_PRIVATE_KEY_ACCESS_DENIED»:-134,
«ERR_SSL_CLIENT_AUTH_SIGNATURE_FAILED»:-141,
«ERR_SSL_DECOMPRESSION_FAILURE_ALERT»:-125,
«ERR_SSL_DECRYPT_ERROR_ALERT»:-153,
«ERR_SSL_HANDSHAKE_NOT_COMPLETED»:-148,
«ERR_SSL_NO_RENEGOTIATION»:-123,
«ERR_SSL_OBSOLETE_CIPHER»:-172,
«ERR_SSL_PINNED_KEY_NOT_IN_CERT_CHAIN»:-150,
«ERR_SSL_PROTOCOL_ERROR»:-107,
«ERR_SSL_RENEGOTIATION_REQUESTED»:-114,
«ERR_SSL_SERVER_CERT_BAD_FORMAT»:-167,
«ERR_SSL_SERVER_CERT_CHANGED»:-156,
«ERR_SSL_UNRECOGNIZED_NAME_ALERT»:-159,
«ERR_SSL_VERSION_OR_CIPHER_MISMATCH»:-113,
«ERR_SSL_WEAK_SERVER_EPHEMERAL_DH_KEY»:-129,
«ERR_SYN_REPLY_NOT_RECEIVED»:-332,
«ERR_TEMPORARILY_THROTTLED»:-139,
«ERR_TIMED_OUT»:-7,

«ERR_TOO_MANY_REDIRECTS»:-310,
«ERR_TUNNEL_CONNECTION_FAILED»:-111,
«ERR_UNABLE_TO_REUSE_CONNECTION_FOR_PROXY_AUTH»:-170,
«ERR_UNDOCUMENTED_SECURITY_LIBRARY_STATUS»:-344,
«ERR_UNEXPECTED»:-9,
«ERR_UNEXPECTED_PROXY_AUTH»:-323,
«ERR_UNEXPECTED_SECURITY_LIBRARY_STATUS»:-342,
«ERR_UNKNOWN_URL_SCHEME»:-302,
«ERR_UNRECOGNIZED_FTP_DIRECTORY_LISTING_FORMAT»:-334,
«ERR_UNSAFE_PORT»:-312,»ERR_UNSAFE_REDIRECT»:-311,
«ERR_UNSUPPORTED_AUTH_SCHEME»:-339,
«ERR_UPLOAD_FILE_CHANGED»:-14,
«ERR_UPLOAD_STREAM_REWIND_NOT_SUPPORTED»:-25,
«ERR_WINSOCK_UNEXPECTED_WRITTEN_BYTES»:-124,
«ERR_WS_PROTOCOL_ERROR»:-145,
«ERR_WS_THROTTLE_QUEUE_TOO_LARGE»:-154,

При открытии сайтов в браузере иногда возникают ошибки – домен в адресной строке выделяется красным с зачеркиванием или ресурс вообще не открывается. Типовая причина скрывается в сбоях работы сертификата SSL. Исправить их может только администратор сайта, но перед обращением к нему стоит проверить собственный компьютер.

Что такое SSL

Текущие тенденции сайтостроения предполагают высокую безопасность соединения пользователя с веб-ресурсом. Это необходимо для защиты персональных данных, секретных номеров банковских карт и информации о проводимых сделках. Организуется безопасность подключением протокола шифрования Secure Sockets Layer (сокращенно SSL).

Особенности сертификата:

1. Сертификат выпускается доверенным центром Certification Authority (CA).
2. После выдачи он подключается к домену средствами провайдера хостинга.
3. Срок его действия ограничен 1 годом, после чего требуется продление.

Работа сайта возможна и без SSL, но поисковые системы «не доверяют» таким ресурсам и помечают их в браузере как неблагонадежные. Поэтому лучше разобраться, как решить проблему с защитой и полноценно пользоваться протоколом HTTPS. Сертификат актуален на сайтах, где присутствует регистрация, предлагается покупка товаров или онлайн-оплата различных сервисов.

При появлении любых сомнений в исправности защиты регистрироваться на сайте или вводить ранее выданные логин и пароль не рекомендуется. Тем более не стоит осуществлять онлайн-оплату с банковских карт или электронных кошельков, ведь не исключено, что проблема возникла из-за взлома ресурса злоумышленниками.

Причины появления ошибок SSL

Существует всего две причины, почему браузер отображает ошибку сертификата SSL со стороны сервера. Первая заключается в окончании срока активации, вторая – это покупка сертификата у поставщика без достаточных полномочий для выдачи «полноценной защиты». Например, виной может быть выбор самоподписанного сертификата, лишь эмулирующего работу реального протокола.

Остальные проблемы обычно скрываются на локальном компьютере:

1. Произошел сброс системного времени.
2. Неправильно настроена антивирусная программа.
3. Сбоит браузер или установленное расширение.
4. Срабатывает вредоносный скрипт.

Чтобы выяснить настоящую причину, пользователю браузера рекомендуется проверить все перечисленные факторы. При том же заражении компьютерными вирусами возможно проявление сразу нескольких симптомов – от изменения текущего времени и блокировки антивирусом до подключения перенаправления страниц в браузере и других неприятностей.

Изредка встречаются ситуации, когда проблема возникла со стороны администратора, если он ошибся при подключении нового сертификата или забыл продлить его действие. Обычно такие неполадки устраняются быстро, потому что после активации сайт проверяется и, в случае неработоспособности сертификата, проводится повторное подключение вплоть до получения положительного результата.

Время и дата

Сертификат SSL имеет четко обозначенный срок действия с датой активации и деактивации. Такой подход отчасти дает дополнительную защиту, потому что в случае технического сбоя в системных часах компьютера сайты перестают открываться. Сброс времени обычно происходит «назад», на дату изготовления материнской платы, на что и реагирует система.

Варианты исправления ситуации:

1. Вручную внести корректную дату и время, после чего обновить страницу в браузере.
2. Воспользоваться функцией синхронизации через интернет, встроенной в Windows.
3. Заменить батарейку на памяти BIOS. При первом запуске ПК нужно внести корректные данные.

Каждый раз после изменения времени рекомендуется ручное обновление страницы или перезапуск браузера. Такой шаг активирует повторное соединение с сервером и позволяет зайти на сайт «с нуля», но уже с правильным временем, соответствующим сроку действия сертификата SSL (после активации и до ее завершения).

Настройки антивируса и брандмауэра

Программы для защиты компьютера от вирусов и хакерских атак иногда блокируют и «полезные» соединения, например, определенные домены или сразу весь протокол HTTPS, используемый при подключении сертификата SSL. Большинство антивирусов и брандмауэров проверяют его работу, и это становится причиной блокировки сайта как «злоумышленника, пытающего украсть данные».

Варианты исправления ситуации:

1. Отключить режим «проверка протокола HTTPS». После этого зайти на сайт заново.
2. Полностью выключить антивирусную программу. Перезагрузить ПК, открыть страницу.
3. Сбросить настройки брандмауэра. Опять проводится перезапуск компьютера и веб-ресурса.

Функция временного отключения имеется в любой защитной программе, даже интегрированной в операционную систему Windows. Но это не гарантирует полную деактивацию приложения. В этом случае разобраться в ситуации поможет открытие сайта на другом компьютере или запуск безопасного режима (актуально для проводного подключения к интернету).

Браузер и операционная система

Наличие проблемы с браузером проще всего определить открытием сайта на другом устройстве или в другой программе. Иногда решение заключается в банальном обновлении версии приложения до актуальной. То же относится к операционной системе, если используется интегрированный браузер вроде Edge. Пакеты обновлений для того и выпускаются, чтобы устранять неполадки в ПО.

Варианты исправления ситуации:

1. Полностью очистить историю браузера вместе с кэшем и другими данными.
2. Временно отключить все ранее установленные и активные расширения.
3. Переустановить программу после ее полной деинсталляции.

Остается еще один вариант – сбросить настройки браузера до состояния «по умолчанию». Способ аналогичен переустановке, но экономит время. Правда, он неэффективен, если проблема возникла из-за сбоя в одном из служебных файлов программы. Отдельное внимание стоит уделить расширению, выполняющему функции антивирусной защиты, ведь оно часто блокирует даже безопасное соединение.

Заражение компьютерными вирусами

Выдачей ошибки SSL браузер, вероятно, предупреждает о попытке его подмены, переадресации на сайт-клон или иной угрозе. В это случае рекомендуется провести полную проверку компьютера на наличие вирусов. Если присутствуют другие признаки заражения, стоит скачать парочку программ со свежими антивирусными базами (например, CureIt).

Варианты исправления ситуации:

1. Временно отключить все программы из автозагрузки.
2. Провести очистку диска от временных файлов.
3. Перезагрузить компьютер после предыдущих шагов.

Выполняются перечисленные действия программами типа CCleaner. Они дают прямой доступ как к автозагрузке операционной системе, так и к списку расширений установленных браузеров. Также в таких программах обычно есть функция удаления ненужных системных файлов, в которых запросто может быть тело компьютерного вируса.

Если предложенные способы устранения ошибки SSL не помогли, остается ждать, пока проблему устранит администратор, или воспользоваться любым другим тематическим сайтом с аналогичным контентом.

It’s never been easier to obtain a Secure Sockets Layer (SSL) certificate for your website and set it up. But you can still run into SSL connection errors even after installing your certificate correctly and forcing traffic through HTTPS. In many cases, these error messages can drive users away.

Understanding what causes SSL errors will help you prevent them from popping up on your website. You’ll also know what to do if you run into one, depending on the message you see and the browser or OS you’re using.

In this article, we’ll explore what SSL connection errors are and their leading causes. We’ll also discuss their most common types and how you can troubleshoot them.

Let’s get to it!

Check Out Our Video Guide to Fixing SSL Connection Errors

What Is an SSL Connection Error?

There are several types of SSL connection errors that you may encounter while browning the web. Some of these errors are due to server-side issues, whereas others are because of local configuration problems.

In broad terms, SSL connection errors will prevent you from browsing a website securely over Hypertext Transfer Protocol Secure (HTTPS). Your browser may allow you to proceed with the connection, but in most cases, it’ll tell you that you’re doing so at your own risk. Without a valid SSL certificate, malicious parties can intercept any data you exchange with the website you’re trying to view.

Some of the most common SSL connection errors that you may run into include:

• NET:ERR_CERT_AUTHORITY_INVALID
• NET::ERR_CERT_COMMON_NAME_INVALID
• NET::ERR_CERT_REVOKED
• SSL Handshake Failed
• ERR_SSL_OBSOLETE_VERSION
• ERR_SLL_PROTOCOL_ERROR

Each type of SSL connection error points towards a different cause. When you run into such a problem, your browser will display a specific message that gives you information about why you see it:

It’s important to note that error messages can vary from one browser to another. The one pictured above comes from Firefox, whereas the one below pops up when we open the same website using Chrome:

As mentioned before, not all SSL connection errors stem from problems with your server configuration. Your website can have a perfectly valid SSL certificate, but users might still run into errors when accessing it.

Throughout the following few sections, we’ll show you what to do if you’re trying to access a website and you run into SSL connection issues.

It’s never been easier to obtain an SSL certificate for your website and set it up… but errors can still occur. 😅 Learn how to fix them with this guide ⬇️Click to Tweet

How to Fix SSL Connection Errors (8 Methods)

If you’re not in charge of a website, there’s little that you can do when it comes to fixing server-side SSL connection errors. However, some issues can occur due to problems with your local device or browser configuration.

We’ll show you how to fix local issues that cause SSL connection errors using various browsers, mobile OSs, and social media platforms.

Let’s get fixing!

1. How to Fix the SSL Connection Error in Google Chrome

If you run into an SSL connection error in Google Chrome, there are several quick fixes that you can implement.

First off, make sure you’re running the latest version of Chrome. You can update Chrome from within the browser itself, or you can download and install the most recent version from Google Chrome’s website.

Next, check if your system’s time and date are synchronized. If your device’s time is not correct, you may run into SSL connection issues throughout the web because some SSL certificates rely on internal system clocks for validation. An incorrect time or date on your computer can lead to errors as your browser can’t verify these certificates.

On Windows, you can fix the time and date by opening the Settings menu and selecting the Time & Language option:

On the next screen, make sure that both the Set the time automatically and Set the time zone automatically options are enabled. Alternatively, you can select your time zone manually and enable the Set the date and time manually option:

If you’re using Chrome on macOS, open the System Preferences menu by clicking on the Apple icon in the top left corner of the screen. Select the Date & Time option and enable the Set date and time automatically setting:

Once you fix the date and time, try accessing the website that showed an SSL connection error in Chrome. If the problem persists, move on to clearing your Chrome cache and cookies. To do so, open the Settings menu and click on Clear browsing data.

A window will pop up, enabling you to select what data you want to clear. If you’re using the Basic settings, select Cookies and other site data and Cached images and files, then hit the Clear data button:

Another fix that you can try is to clear the SSL slate in your operating system. To do so in Windows, open the start menu and search for Internet Options. Click on the result that comes up, and an Internet Properties window will pop up. Jump to Content and click on Clear SSL slate:

Clearing the SSL slate will remove all of the certificates stored locally on your computer. The next time you reload the website giving you SSL connection errors, the browser will attempt to re-validate its certificate and, in doing so, might clear the error.

If you’re using macOS, clearing your SSL slate works a bit differently. Open your Utilities menu and go to Keychain Access. Select the System option under Keychains in the left-hand menu, and you’ll see an overview of all the SSL certificates that your system stores locally:

You can select certificates individually and delete them manually. If you spot a certificate for the website you’re trying to access, delete that one first, then check to see if the SSL connection error persists.

At this stage, if all else fails, temporarily disable your antivirus software and firewall. We suggest this as a last resort because, in most cases, your antivirus software won’t cause issues with SSL connections.

If you try every fix and nothing works, you can assume that the SSL connection problem lies with the server.

2. How to Fix the SSL Connection Error in Firefox

Fixing SSL connection errors in Firefox works much the same as with other browsers. You can follow the instructions in the last section to implement the following fixes:

1. Check your system’s date and time and adjust them.
2. Clear your local SSL slate.

If neither of those solutions works, then it’s time to clear your Firefox cookies and cache. To do so, go to the Options menu and jump to the Privacy & Security tab. Then click on the Clear Data button under Cookies and Site Data:

Try accessing the website with the SSL connection error once more. If your browser fails to establish a connection, check to see whether there’s a new version of Firefox that you can update.

3. How to Fix the SSL Connection Error in Safari

So far, we’ve covered multiple fixes for the SSL connection error that work across OSs. If you’re using Safari, start by following the same instructions given under the Google Chrome section:

1. Check your system’s date and time and adjust them.
2. Clear your local SSL slate in macOS.

If the SSL connection error persists, you can move forward and clear your Safari cookies and cache. If you’re using an iMac, Macbook, iPhone, or iPad, the exact instructions apply here:

1. Open the Safari Settings menu.
2. Click on Clear History.

With that out of the way, try to access the website that gave you an SSL connection error before. The error should be gone now unless you’re dealing with a server-side configuration issue.

4. How to Fix the SSL Connection Error on iPhones and iPads

The process for fixing the SSL connection error on an iPhone or an iPad is identical to doing so on macOS. First, you need to check if your device’s date and time are synchronized. To access your mobile device’s date and time settings:

1. Open the Settings app and select General > Date & Time.
2. Check if the Set Automatically option is enabled. If it isn’t, turn it on.
3. Manually check if your device is using the correct time zone.

After updating your date and time settings, you can move on to clearing your browser’s cookies and cache. To do so, open the Settings app and select Safari > Clear History and Website Data:

If you’ve installed a different browser on your iOS device, the process should still be similar.

Unfortunately, the most recent versions of iOS have removed the option to clear your SSL slate on your iPhone or iPad, so this is not a viable solution. If none of the fixes above work, you can assume the problem is server-side.

5. How to Fix the SSL Connection Error on Android

Fixing the SSL connection error on Android is relatively simple. First, go ahead and check your time and date settings to see if they’re accurate.

Open the Settings app and tap on General Management > Date and time. Then check if the Automatic date and time setting is enabled:

It’s important to note that, like iOS, Android doesn’t include an option for clearing your SSL slate or deleting individual certificates. What you can do to fix SSL connection errors is to clear your Chrome browsing data. To do so:

1. Open the Chrome browser and access its Settings menu.
2. Go to Privacy and security.
3. Tap on Clear browsing data.
4. Select your browser’s Cookies and site data and Cached images and files options, then tap on Clear data.

After clearing your Chrome website data, check if the SSL connection error persists. If it does, the chances are that it’s a server-side configuration issue.

6. How to Fix the SSL Connection Error on Facebook

If you run into an SSL connection error on Facebook, you can be sure that it’s not a server-side issue. That means you’re dealing with a local configuration problem. Here are the fixes that you should implement:

1. Adjust your local time and date settings.
2. Clear your browser’s cache and cookies.
3. Clear your OS’s SSL slate or delete any local certificates for Facebook.

You can find instructions about adjusting your date and time settings on Windows and macOS within the Google Chrome section of this article. We also have instructions on clearing your browser’s cookies and cache for Chrome, Firefox, and Safari.

7. How to Fix the SSL Connection Error on Gmail

You won’t run into SSL connection errors while trying to access Gmail using mobile apps. However, SSL errors might pop up if you’re using Chrome, Firefox, or Safari to access Gmail’s web service. In that case, you should:

1. Adjust your local time and date settings (check the Google Chrome section above for instructions).
2. Clear your browser’s cache and cookies.
3. Clear your OS’s SSL slate or delete any local certificates for Gmail.

If everything else fails, you can access Gmail using a mobile app while you try disabling your firewall temporarily or updating your browser to its latest version.

8. How to Fix the SSL Connection Error on YouTube

SSL connection errors on YouTube are likely due to local configuration errors within your OS or browser. If you run into an SSL error in YouTube:

1. Adjust your local time and date settings (check the Google Chrome section above for instructions).
2. Clear your browser’s cache and cookies.
3. Clear your OS’s SSL slate or delete any local certificates from YouTube.

We provided instructions on clearing your browser’s cache and cookies for Chrome, Firefox, and Safari earlier in this post. Likewise, you can find step-by-step guides on how to clear your SSL slate by checking the Chrome and Safari instructions in the previous sections.

Don’t let SSL errors bring you down 🙅‍♂️ Learn how to quickly troubleshoot them right here ✅Click to Tweet

Summary

SSL connection errors can come in a lot of shapes and sizes. If you’re dealing with a server-side error, there’s often little that you can do except wait for the site’s owner to fix it or proceed with an unsafe connection.

That said, you can attempt several local configuration fixes that may solve this issue, including:

1. Adjusting your time and date settings.
2. Clearing your browser’s cookies and cache.
3. Clearing your OS’s SSL slate.

If you’re still facing SSL connection errors with your website, please leave a comment below. Kinsta clients can also reach out to our support team to get any SSL errors fixed.

It’s never been easier to obtain a Secure Sockets Layer (SSL) certificate for your website and set it up. But you can still run into SSL connection errors even after installing your certificate correctly and forcing traffic through HTTPS. In many cases, these error messages can drive users away.

Understanding what causes SSL errors will help you prevent them from popping up on your website. You’ll also know what to do if you run into one, depending on the message you see and the browser or OS you’re using.

In this article, we’ll explore what SSL connection errors are and their leading causes. We’ll also discuss their most common types and how you can troubleshoot them.

Let’s get to it!

Check Out Our Video Guide to Fixing SSL Connection Errors

What Is an SSL Connection Error?

There are several types of SSL connection errors that you may encounter while browning the web. Some of these errors are due to server-side issues, whereas others are because of local configuration problems.

In broad terms, SSL connection errors will prevent you from browsing a website securely over Hypertext Transfer Protocol Secure (HTTPS). Your browser may allow you to proceed with the connection, but in most cases, it’ll tell you that you’re doing so at your own risk. Without a valid SSL certificate, malicious parties can intercept any data you exchange with the website you’re trying to view.

Some of the most common SSL connection errors that you may run into include:

• NET:ERR_CERT_AUTHORITY_INVALID
• NET::ERR_CERT_COMMON_NAME_INVALID
• NET::ERR_CERT_REVOKED
• SSL Handshake Failed
• ERR_SSL_OBSOLETE_VERSION
• ERR_SLL_PROTOCOL_ERROR

Each type of SSL connection error points towards a different cause. When you run into such a problem, your browser will display a specific message that gives you information about why you see it:

It’s important to note that error messages can vary from one browser to another. The one pictured above comes from Firefox, whereas the one below pops up when we open the same website using Chrome:

As mentioned before, not all SSL connection errors stem from problems with your server configuration. Your website can have a perfectly valid SSL certificate, but users might still run into errors when accessing it.

Throughout the following few sections, we’ll show you what to do if you’re trying to access a website and you run into SSL connection issues.

It’s never been easier to obtain an SSL certificate for your website and set it up… but errors can still occur. 😅 Learn how to fix them with this guide ⬇️Click to Tweet

How to Fix SSL Connection Errors (8 Methods)

If you’re not in charge of a website, there’s little that you can do when it comes to fixing server-side SSL connection errors. However, some issues can occur due to problems with your local device or browser configuration.

We’ll show you how to fix local issues that cause SSL connection errors using various browsers, mobile OSs, and social media platforms.

Let’s get fixing!

1. How to Fix the SSL Connection Error in Google Chrome

If you run into an SSL connection error in Google Chrome, there are several quick fixes that you can implement.

First off, make sure you’re running the latest version of Chrome. You can update Chrome from within the browser itself, or you can download and install the most recent version from Google Chrome’s website.

Next, check if your system’s time and date are synchronized. If your device’s time is not correct, you may run into SSL connection issues throughout the web because some SSL certificates rely on internal system clocks for validation. An incorrect time or date on your computer can lead to errors as your browser can’t verify these certificates.

On Windows, you can fix the time and date by opening the Settings menu and selecting the Time & Language option:

On the next screen, make sure that both the Set the time automatically and Set the time zone automatically options are enabled. Alternatively, you can select your time zone manually and enable the Set the date and time manually option:

If you’re using Chrome on macOS, open the System Preferences menu by clicking on the Apple icon in the top left corner of the screen. Select the Date & Time option and enable the Set date and time automatically setting:

Once you fix the date and time, try accessing the website that showed an SSL connection error in Chrome. If the problem persists, move on to clearing your Chrome cache and cookies. To do so, open the Settings menu and click on Clear browsing data.

A window will pop up, enabling you to select what data you want to clear. If you’re using the Basic settings, select Cookies and other site data and Cached images and files, then hit the Clear data button:

Another fix that you can try is to clear the SSL slate in your operating system. To do so in Windows, open the start menu and search for Internet Options. Click on the result that comes up, and an Internet Properties window will pop up. Jump to Content and click on Clear SSL slate:

Clearing the SSL slate will remove all of the certificates stored locally on your computer. The next time you reload the website giving you SSL connection errors, the browser will attempt to re-validate its certificate and, in doing so, might clear the error.

If you’re using macOS, clearing your SSL slate works a bit differently. Open your Utilities menu and go to Keychain Access. Select the System option under Keychains in the left-hand menu, and you’ll see an overview of all the SSL certificates that your system stores locally:

You can select certificates individually and delete them manually. If you spot a certificate for the website you’re trying to access, delete that one first, then check to see if the SSL connection error persists.

At this stage, if all else fails, temporarily disable your antivirus software and firewall. We suggest this as a last resort because, in most cases, your antivirus software won’t cause issues with SSL connections.

If you try every fix and nothing works, you can assume that the SSL connection problem lies with the server.

2. How to Fix the SSL Connection Error in Firefox

Fixing SSL connection errors in Firefox works much the same as with other browsers. You can follow the instructions in the last section to implement the following fixes:

1. Check your system’s date and time and adjust them.
2. Clear your local SSL slate.

If neither of those solutions works, then it’s time to clear your Firefox cookies and cache. To do so, go to the Options menu and jump to the Privacy & Security tab. Then click on the Clear Data button under Cookies and Site Data:

Try accessing the website with the SSL connection error once more. If your browser fails to establish a connection, check to see whether there’s a new version of Firefox that you can update.

3. How to Fix the SSL Connection Error in Safari

So far, we’ve covered multiple fixes for the SSL connection error that work across OSs. If you’re using Safari, start by following the same instructions given under the Google Chrome section:

1. Check your system’s date and time and adjust them.
2. Clear your local SSL slate in macOS.

If the SSL connection error persists, you can move forward and clear your Safari cookies and cache. If you’re using an iMac, Macbook, iPhone, or iPad, the exact instructions apply here:

1. Open the Safari Settings menu.
2. Click on Clear History.

With that out of the way, try to access the website that gave you an SSL connection error before. The error should be gone now unless you’re dealing with a server-side configuration issue.

4. How to Fix the SSL Connection Error on iPhones and iPads

The process for fixing the SSL connection error on an iPhone or an iPad is identical to doing so on macOS. First, you need to check if your device’s date and time are synchronized. To access your mobile device’s date and time settings:

1. Open the Settings app and select General > Date & Time.
2. Check if the Set Automatically option is enabled. If it isn’t, turn it on.
3. Manually check if your device is using the correct time zone.

After updating your date and time settings, you can move on to clearing your browser’s cookies and cache. To do so, open the Settings app and select Safari > Clear History and Website Data:

If you’ve installed a different browser on your iOS device, the process should still be similar.

Unfortunately, the most recent versions of iOS have removed the option to clear your SSL slate on your iPhone or iPad, so this is not a viable solution. If none of the fixes above work, you can assume the problem is server-side.

5. How to Fix the SSL Connection Error on Android

Fixing the SSL connection error on Android is relatively simple. First, go ahead and check your time and date settings to see if they’re accurate.

Open the Settings app and tap on General Management > Date and time. Then check if the Automatic date and time setting is enabled:

It’s important to note that, like iOS, Android doesn’t include an option for clearing your SSL slate or deleting individual certificates. What you can do to fix SSL connection errors is to clear your Chrome browsing data. To do so:

1. Open the Chrome browser and access its Settings menu.
2. Go to Privacy and security.
3. Tap on Clear browsing data.
4. Select your browser’s Cookies and site data and Cached images and files options, then tap on Clear data.

After clearing your Chrome website data, check if the SSL connection error persists. If it does, the chances are that it’s a server-side configuration issue.

6. How to Fix the SSL Connection Error on Facebook

If you run into an SSL connection error on Facebook, you can be sure that it’s not a server-side issue. That means you’re dealing with a local configuration problem. Here are the fixes that you should implement:

1. Adjust your local time and date settings.
2. Clear your browser’s cache and cookies.
3. Clear your OS’s SSL slate or delete any local certificates for Facebook.

You can find instructions about adjusting your date and time settings on Windows and macOS within the Google Chrome section of this article. We also have instructions on clearing your browser’s cookies and cache for Chrome, Firefox, and Safari.

7. How to Fix the SSL Connection Error on Gmail

You won’t run into SSL connection errors while trying to access Gmail using mobile apps. However, SSL errors might pop up if you’re using Chrome, Firefox, or Safari to access Gmail’s web service. In that case, you should:

1. Adjust your local time and date settings (check the Google Chrome section above for instructions).
2. Clear your browser’s cache and cookies.
3. Clear your OS’s SSL slate or delete any local certificates for Gmail.

If everything else fails, you can access Gmail using a mobile app while you try disabling your firewall temporarily or updating your browser to its latest version.

8. How to Fix the SSL Connection Error on YouTube

SSL connection errors on YouTube are likely due to local configuration errors within your OS or browser. If you run into an SSL error in YouTube:

1. Adjust your local time and date settings (check the Google Chrome section above for instructions).
2. Clear your browser’s cache and cookies.
3. Clear your OS’s SSL slate or delete any local certificates from YouTube.

We provided instructions on clearing your browser’s cache and cookies for Chrome, Firefox, and Safari earlier in this post. Likewise, you can find step-by-step guides on how to clear your SSL slate by checking the Chrome and Safari instructions in the previous sections.

Don’t let SSL errors bring you down 🙅‍♂️ Learn how to quickly troubleshoot them right here ✅Click to Tweet

Summary

SSL connection errors can come in a lot of shapes and sizes. If you’re dealing with a server-side error, there’s often little that you can do except wait for the site’s owner to fix it or proceed with an unsafe connection.

That said, you can attempt several local configuration fixes that may solve this issue, including:

1. Adjusting your time and date settings.
2. Clearing your browser’s cookies and cache.
3. Clearing your OS’s SSL slate.

If you’re still facing SSL connection errors with your website, please leave a comment below. Kinsta clients can also reach out to our support team to get any SSL errors fixed.