The SSL connection could not be established, see inner exception error
Overview
When configuring a license in Easy2Patch, the following error may be displayed:
The SSL connection could not be established, see inner exception.
This error indicates that Easy2Patch was unable to establish a secure HTTPS connection to the license service.
The following steps can be used to verify network connectivity and identify whether the issue is related to DNS resolution, firewall rules, proxy configuration, or SSL/TLS connectivity.
Prerequisites
Before performing the troubleshooting steps, verify the following:
The tests are performed on the Easy2Patch Server.
PowerShell is started with appropriate permissions.
The server has outbound HTTPS connectivity.
The required firewall rules allow communication with the Easy2Patch license service.
The following endpoint must be reachable:
license.arksoft.com.tr
HTTPS
TCP 443
Step 1: Verify Website Accessibility
Open a web browser on the Easy2Patch Server and navigate to:
https://license.arksoft.com.tr
Expected result
The endpoint should be reachable without a connection timeout or SSL/TLS-related error.
If the endpoint cannot be accessed through the browser, continue with the PowerShell connectivity tests below.
Step 2: Verify DNS Resolution
Open PowerShell and run the following command:
Expected result
The command should return the IP address associated with the endpoint.
Example:
If the test fails
If the command returns a DNS-related error, verify the DNS configuration of the Easy2Patch Server and ensure that license.arksoft.com.tr can be resolved by the configured DNS servers.
Step 3: Verify TCP Port 443 Connectivity
Run the following command:
Expected result
The following value should be returned:
Example:
If the test fails
If the following result is returned:
the Easy2Patch Server cannot establish a TCP connection to the license service on port 443.
In this case, verify the outbound firewall rules and ensure that the following communication is permitted:
Source: Easy2Patch Server
Destination: license.arksoft.com.tr
Protocol: HTTPS
Port: TCP 443
Direction: Outbound
Step 4: Verify HTTPS Connectivity
If TCP port 443 is accessible, verify that an HTTPS connection can be established.
Run:
Expected result
The command should return an HTTP response from the license service.
For example:
An HTTP response such as 200, 401, 403, or 404 can still indicate that the HTTPS connection itself was successfully established. The important point is that the request does not fail during the SSL/TLS connection stage.
If the test fails
If an error such as the following is returned:
or:
further investigation of the SSL/TLS, proxy, certificate, or firewall configuration is required.
Step 5: Verify TLS 1.2 Connectivity
To explicitly test the connection using TLS 1.2, run:
Expected result
An HTTP response should be returned from the license service.
If the request fails with an SSL/TLS-related error, check whether the environment uses:
SSL inspection
HTTPS inspection
An outbound proxy
TLS interception
Custom certificate authorities
Firewall-based TLS filtering
Step 6: Perform a Detailed TLS Connection Test
For additional troubleshooting information, run:
Expected result
The output should indicate that the connection and TLS handshake were successfully established.
For example:
The command should then return an HTTP response from the endpoint.
Common failure scenarios
DNS resolution failed
DNS configuration
TcpTestSucceeded : False
Firewall or network restriction
Connection timeout
Firewall, proxy, or routing issue
SSL certificate error
Certificate trust or SSL inspection
TLS handshake failure
TLS configuration or SSL inspection
HTTPS request successful but E2P fails
Application/service-specific configuration
Required Firewall Configuration
The following outbound communication should be permitted from the Easy2Patch Server:
Easy2Patch Server
license.arksoft.com.tr
HTTPS
TCP 443
Outbound
If the customer's environment uses a web proxy or SSL inspection solution, the endpoint may also need to be excluded from SSL/TLS inspection to allow the Easy2Patch license service to establish the required secure connection.
Information to Collect
If the issue persists, collect the output of the following commands from the Easy2Patch Server:
These results can be used to determine whether the issue is related to DNS resolution, network connectivity, firewall configuration, proxy settings, or SSL/TLS negotiation.
Last updated