Friday 24 November 2023

10 ways to fix error during ssl handshake with remote server ?


error-during-ssl-handshake-with-remote- server.png

What is error during ssl handshake with remote server ?

An SSL handshake error can occur for various reasons. Ensure that the server's SSL certificate is valid, check if your system's date and time are accurate, and verify that there are no network issues. Additionally, make sure your client supports the SSL/TLS version expected by the server. If the problem persists, providing more details about the error message or the context could help in troubleshooting.This error occurs when the client and the server fail to establish a secure connection during the SSL handshake process. This can happen for various reasons, such as:

🟒- The client and the server are using different SSL versions or Cipher Suites.

🟒- The server's certificate is not trusted by the client or the client's certificate is not trusted by the server¹².

🟒- The server's certificate is expired, revoked, or malformed³.

🟒- The server's proxy settings are not configured properly.

To quick fix this error during ssl handshake with remote server?

🟒- Check the SSL version and Cipher Suite that the client and the server are using and make sure they are compatible¹.

🟒- Verify the server's certificate and the client's certificate and make sure they are valid and trusted².

🟒- Update the server's certificate if it is expired or revoked.

🟒- Adjust the server's proxy settings to allow SSL communication with the remote server. You may need to add some directives to your Apache configuration file, such as SSLProxyEngine, SSLProxyVerify, SSLProxyCheckPeerCN, SSLProxyCheckPeerName, and SSLProxyCheckPeerExpire.

error during ssl handshake with remote server how to fixed permanently?

error-during-ssl-handshake-with-remote- server.png

To fix an SSL handshake error with a remote server, you can follow these steps:

1. **Check System Date and Time:**

   Ensure that the date and time on your system are correct. SSL certificates have expiration dates, and an incorrect system time may cause handshake failures.

To check the date and time on your system:

- On Windows:

  - Right-click on the clock in the taskbar.

  - Select "Adjust date/time."

  - Verify that the date and time are set correctly.

- On macOS:

  - Click on the Apple menu and choose "System Preferences."

  - Select "Date & Time."

  - Ensure that the "Set date and time automatically" option is checked.

- On Linux:

  - Open a terminal.

  - Type `date` and press Enter to display the current date and time.

  - If needed, use the `date` command to set the correct date and time.

Ensure that the date and time are accurate, as SSL certificates rely on correct system time for validation.

2. **Verify Certificate Validity:**

   Confirm that the SSL certificate on the remote server is valid and has not expired. If it has, you may need to renew or replace it.

To verify the SSL certificate validity of a remote server, you can use various methods:

1. **Web Browser:**

   - Visit the website in a web browser.

   - Click on the padlock icon in the address bar.

   - View the certificate details, including its validity period.

2. **Command Line (Linux/Unix):**

   - Use the `openssl` command in the terminal:


     openssl s_client -connect | openssl x509 -noout -dates


     Replace `` with the actual domain.

3. **Online Tools:**

   - Use online SSL certificate checker tools.

   - Enter the website's domain, and the tool will display certificate details, including validity.

4. **Certificate Authorities' Websites:**

   - Some Certificate Authorities have online tools to check certificate validity.

   - Visit the CA's website and look for a certificate check option.

5. **Security Tools:**

   - Security scanning tools or vulnerability scanners often include SSL certificate checks.

   - Run a security scan on the website to get detailed information.

Ensure that the certificate is not expired and is issued by a trusted Certificate Authority. If you encounter issues, it may be worth reaching out to the website administrator or the entity responsible for managing the SSL certificate.

3. **Update SSL/TLS Libraries:**

   Ensure that your SSL/TLS libraries on both the client and server sides are up-to-date. Outdated libraries may have vulnerabilities or compatibility issues.

To update SSL/TLS libraries on your system, follow these general steps:

1. **Operating System Updates:**

   - Ensure your operating system is up-to-date with the latest security patches and updates.

   - On Linux, use package managers like `apt`, `yum`, or `zypper` to update the system.

   - On Windows, run Windows Update to get the latest updates.

2. **Browser Updates:**

   - If you're encountering SSL/TLS issues in a web browser, make sure your browser is updated to the latest version.

   - Check for updates in the browser settings or preferences.

3. **Application Updates:**

   - If SSL/TLS is used by a specific application, ensure that the application is updated to the latest version.

   - Check the application's settings or documentation for information on updates.

4. **Library-Specific Updates:**

   - For server-side applications, update the SSL/TLS libraries used by the server.

   - On Linux, this might involve updating OpenSSL, GnuTLS, or other libraries.

   - On Windows, ensure that the libraries used by your server software are up-to-date.

5. **Compile from Source (if necessary):**

   - In some cases, you may need to compile and install SSL/TLS libraries manually from source.

   - Refer to the official documentation of the specific library for instructions.

6. **Consider Dependency Management:**

   - If your application relies on a specific version of an SSL/TLS library, ensure that updating won't break compatibility with other dependencies.

   - Review the release notes of the library for any breaking changes.

7. **Restart Services:**

   - After updating SSL/TLS libraries, restart relevant services or applications to apply the changes.

Always exercise caution when updating critical components, especially if your system is in a production environment. It's a good practice to test updates in a controlled environment before applying them to a live system. Additionally, refer to the documentation of the specific libraries and tools you are using for detailed instructions on updating.

4. **Check Cipher Suites:**

   Confirm that the cipher suites supported by your client match those supported by the server. Sometimes, a mismatch can cause handshake failures.

To check the cipher suite supported by a server, you can use the `openssl` command in the terminal. Here's an example:


openssl s_client -connect -tls1_2


Replace `` with the actual domain of the server. This command connects to the specified server on port 443 using TLS 1.2 and displays detailed information about the SSL/TLS negotiation, including the cipher suite.

Look for the line that starts with "Cipher," and it will show the cipher suite used in the connection.

For example:


Cipher    : ECDHE-RSA-AES256-GCM-SHA384


This line indicates that the cipher suite used for the connection is ECDHE-RSA-AES256-GCM-SHA384.

Make sure to replace `-tls1_2` with the appropriate version if the server supports a different TLS version. If you encounter any issues or have specific requirements, you can adjust the command accordingly.

5. **Firewall and Antivirus Settings:**

   Check your firewall and antivirus settings to ensure they are not blocking the SSL connection. Temporarily disabling them for testing purposes can help identify if they are causing the issue.

To check firewall and antivirus settings, follow these steps:


1. **Windows:**

   - Open the Control Panel.

   - Navigate to "System and Security" > "Windows Defender Firewall."

   - Ensure that the firewall is not blocking the specific port used for your SSL connection.

   - You may need to create an inbound rule to allow traffic on the relevant port.

2. **macOS:**

   - Open "System Preferences" > "Security & Privacy" > "Firewall."

   - Click the lock icon to make changes, then click "Firewall Options."

   - Ensure that the firewall is not blocking the necessary connections.

3. **Linux:**

   - Firewall settings vary among Linux distributions (e.g., iptables, ufw).

   - Use the relevant command or graphical tool to check and modify firewall rules.


1. **Windows:**

   - Open your antivirus software.

   - Look for settings related to network or firewall.

   - Ensure that it is not blocking the SSL connections.

2. **macOS:**

   - Some security software on macOS may include firewall features.

   - Check the settings of your security software to make sure it's not interfering with your SSL connections.

3. **Third-Party Antivirus:**

   - If you are using third-party antivirus software, check its settings for any features related to network protection or firewall.

   - Ensure that it allows the necessary connections for SSL.

Remember, temporarily disabling your firewall or antivirus for testing purposes can help identify if they are causing the SSL handshake issue. If you do this, exercise caution and only disable these features briefly. If the issue resolves after disabling them, you can then adjust the settings to allow the required connections securely.

6. **Network Issues:**

   Verify that there are no network issues causing packet loss or disruptions during the SSL handshake. A stable and reliable network connection is crucial for successful handshakes.

To troubleshoot network issues affecting SSL handshake with a remote server, consider the following steps:

1. **Ping Test:**

   - Use the `ping` command to check the general connectivity to the remote server.

   - For example: `ping`

2. **Traceroute:**

   - Use the `traceroute` or `tracert` command to trace the route to the server and identify any network hops with high latency.

   - Example: `traceroute` or `tracert`

3. **Firewall Settings:**

   - Confirm that firewalls, both on your end and the server's end, are not blocking the SSL port.

   - Check router/firewall logs for any indication of blocked traffic.

4. **Proxy Settings:**

   - If you are behind a proxy, ensure that your proxy settings are configured correctly.

   - Check if the proxy is allowing SSL traffic.

5. **DNS Resolution:**

   - Ensure that DNS resolution is working correctly. Use the `nslookup` or `dig` command to check the DNS resolution for the server.

   - Example: `nslookup` or `dig`

6. **ISP Issues:**

   - Contact your Internet Service Provider (ISP) to check if there are any known network issues or outages in your area.

7. **Network Traffic Analysis:**

   - Use network monitoring tools like Wireshark to capture and analyze network traffic during the SSL handshake.

   - Look for any abnormalities or errors in the network packets.

8. **MTU Issues:**

   - Check for Maximum Transmission Unit (MTU) issues. Sometimes, reducing the MTU size can resolve connectivity problems.

   - Test with different MTU sizes to find the optimal value.

9. **VPN Connection:**

   - If you are using a VPN, test the connection both with and without the VPN to identify if the VPN is causing the issue.

10. **Check for Service Outages:**

    - Verify if the service or website you are trying to connect to is experiencing downtime. You can use online services that monitor website status.

By systematically checking these aspects, you can identify and resolve network issues affecting the SSL handshake. If the problem persists, reaching out to your network administrator or ISP for further assistance may be necessary.

7. **Update Software:**

   Make sure that your client software (web browser, application, etc.) is updated to the latest version. Updates often include security patches and improvements.

To update software on your system, follow these general steps:

1. **Operating System Updates:**

   - On Windows, run Windows Update to ensure your operating system is up-to-date.

   - On macOS, go to "System Preferences" > "Software Update."

   - On Linux, use your package manager (e.g., `apt`, `yum`, `zypper) to update the system.

2. **Web Browsers:**

   - Update your web browsers to the latest versions.

   - For Chrome, Firefox, Safari, or any other browser, check for updates in the settings or preferences.

3. **Applications:**

   - Update individual applications on your system to the latest versions.

   - Many applications have built-in update mechanisms, or you can check their official websites.

4. **Security Software:**

   - If you have antivirus or security software, ensure it is up-to-date.

   - Check for updates within the software's settings.

5. **Server Software:**

   - If you are running server software, such as a web server (e.g., Apache, Nginx) or database server, update it to the latest version.

   - Refer to the documentation of the specific software for update instructions.

6. **Programming Languages and Frameworks:**

   - If you use programming languages like Python, Java, or frameworks like Node.js, update them to the latest stable versions.

   - Use the respective package managers or update tools for each language.

7. **Development Tools:**

   - Update development tools, IDEs, and other related software.

   - For example, if you use Visual Studio Code, check for updates within the editor.

8. **Dependencies:**

   - If your software relies on third-party libraries or dependencies, update them to the latest compatible versions.

   - Review release notes to ensure compatibility with your existing code.

9. **Restart Applications:**

   - After updating software, especially server-related components, restart the relevant services or applications to apply the changes.

Always back up your important data before performing updates, especially for critical systems. Additionally, if you're working on a development project, ensure that updates do not introduce breaking changes to your codebase.

8. **Debugging Tools:**

   Use debugging tools like Wireshark or browser developer tools to inspect the SSL handshake process. This can provide more detailed information about where the issue is occurring.

To debug SSL handshake issues or other network-related problems, you can use various debugging tools. Here are some commonly used tools:

1. **Wireshark:**

   - A network protocol analyzer that allows you to capture and inspect the data traveling back and forth on your network. It's useful for analyzing SSL/TLS handshakes and identifying issues.

2. **tcpdump:**

   - A command-line packet analyzer available on Unix-like operating systems. It can capture and display packet data on the command line.

3. **cURL:**

   - A command-line tool for making HTTP requests. It supports a wide range of protocols, including HTTPS. You can use it to test SSL connections and view detailed information about the SSL handshake.

4. **OpenSSL:**

   - A toolkit implementing the SSL and TLS protocols. You can use the `openssl` command-line tool to troubleshoot SSL connections, check certificate information, and perform other tasks.



   openssl s_client -connect


5. **Browser Developer Tools:**

   - Most web browsers have built-in developer tools that allow you to inspect network traffic, including SSL handshake details. Access the developer tools by right-clicking on the web page and selecting "Inspect" or using keyboard shortcuts (Ctrl+Shift+I or Cmd+Opt+I).

6. **Fiddler:**

   - A web debugging proxy that can capture, inspect, and modify HTTP and HTTPS traffic between your computer and the internet.

7. **Postman:**

   - A popular API development environment that can be used to send HTTPS requests and inspect responses. It provides a user-friendly interface for testing APIs.

8. **ngrep:**

   - A network grep tool that allows you to search for specific patterns in network traffic. It can be handy for identifying issues in SSL handshakes.

When using these tools, pay attention to error messages, response codes, and timestamps to identify where the issue might be occurring. Always ensure you have the necessary permissions to capture or inspect network traffic, especially when working in production environments.

9. **Contact Server Administrator:**

   If the error persists, contact the administrator of the remote server. They may have insights into server side configurations or issues that could be causing the SSL handshake problem.

If you need to contact the server administrator to address an SSL handshake issue or any other server-related problem, consider the following steps:

1. **Identify Contact Information:**

   - Check the website or service's contact page for information on how to reach the server administrator.

   - Look for contact details such as an email address, support form, or relevant support channels.

2. **WHOIS Lookup:**

   - Use a WHOIS lookup service to find information about the domain and identify administrative contacts.

   - Many domain registrars provide WHOIS lookup tools on their websites.

3. **Check DNS Records:**

   - Examine the DNS records for the domain to see if there are any administrative or technical contacts listed.

   - Use a DNS lookup tool or command-line commands like `nslookup` or `dig` for this purpose.

4. **Website Contact Information:**

   - If the website has a "Contact Us" page, check for relevant information.

   - Some websites provide support email addresses or contact forms.

5. **Look for Server Information:**

   - If possible, determine the hosting provider or data center associated with the server.

   - Reach out to the hosting provider's support for assistance if direct contact information for the server administrator is not available.

6. **Check Security Headers:**

   - Inspect HTTP response headers for any security-related headers like `Contact` or `Security-Contact`.

   - Some websites include contact information in these headers.

7. **Use Social Media:**

   - Check the website or organization's social media profiles for contact information.

   - Sometimes, social media channels are used for support inquiries.

8. **Documentation or Support Forums:**

   - Some websites provide documentation or support forums where you can find assistance or contact administrators.

When reaching out to the server administrator, clearly describe the issue you're facing, including any relevant error messages or details about the SSL handshake problem. Be concise and provide as much information as possible to help expedite the resolution process.

10. **Consider Protocol Versions:**

    Ensure that the SSL/TLS protocol versions supported by your client and server are compatible. Some servers may require specific protocol versions.

Remember to approach these steps systematically, checking one aspect at a time to identify and resolve the SSL handshake issue. If you provide more specific details about the error message or context, I can offer more targeted assistance.

When troubleshooting an SSL handshake error, it's important to consider the protocol version being used by both the client and the server. Here are some steps to check and consider the protocol version:

1. **Check Supported Protocols:**

   - Verify which SSL/TLS protocol versions are supported by your client application and the remote server.

   - This information is often available in the application's settings or configuration files.

2. **Client-Side Configuration:**

   - If you are the owner or administrator of the client application, check its configuration settings to ensure it supports a protocol version compatible with the server.

3. **Server-Side Configuration:**

   - Review the server's SSL/TLS configuration. Ensure it is configured to support a protocol version that is compatible with the client.

   - This configuration is often found in the server's configuration files (e.g., Apache or Nginx).

4. **Update Software Versions:**

   - Ensure that both the client and server software are using relatively recent versions that support modern and secure SSL/TLS protocols.

   - Outdated software versions may lack support for newer protocols or have vulnerabilities.

5. **Check Error Messages:**

   - Review any error messages related to the SSL handshake. They may provide clues about incompatible protocol versions.

   - The error message might indicate a specific protocol version that is causing the issue.

6. **Test with Different Protocols:**

   - If possible, test the connection using different SSL/TLS protocol versions to identify if a specific version is causing the problem.

   - Some applications or tools allow you to specify the protocol version during testing.

7. **Consider Deprecated Protocols:**

   - Be aware of deprecated and insecure SSL/TLS protocols (e.g., SSLv2, SSLv3). Ensure that both client and server are not configured to use these outdated protocols.

8. **Log Analysis:**

   - Check server logs for any information related to the SSL handshake and supported protocol versions.

   - Logs can provide insights into which protocol versions are being negotiated during the handshake.

9. **Update Configuration if Necessary:**

   - If there is a mismatch in protocol versions, update the configuration of either the client or the server to support a common, secure protocol version.

By considering and aligning the SSL/TLS protocol versions between the client and server, you can help ensure a successful handshake and establish a secure connection. If the issue persists, further investigation into specific error messages or logs may be necessary.