Kong / Kong/insomnia

SSL connect error

Open
#1,986 14 comments 0 reactions 0 assignees View on GitHub
N-investigation needs-triage
Dominant language
TypeScript
Stars
40k
Forks
2.4k
Avg merge
2d 13h
Merged PRs (30d)
61

Description

Insomnia can not connect over SSL to windows server with IIS 8 and Let's encrypt certificate (256 bits, TLS 1.2), it returns Error: SSL connect error
Tried with another RESTClient app to check server configuration and works as spected.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to new request
2. Insert the rest endpoint in my case to a Win12K server https://api.privateserverdomaincantpublish.com:8443
4. SSL connect error.

* Preparing request to https://api.privateserverdomaincantpublish:8443/
* Using libcurl/7.67.0 OpenSSL/1.1.1c zlib/1.2.11 nghttp2/1.29.0
* Current time is 2020-03-06T14:51:44.508Z
* Disable timeout
* Enable automatic URL encoding
* Disable SSL validation
* Enable cookie sending with jar of 2 cookies
* Hostname api.privateserverdomaincantpublish.com was found in DNS cache
* Trying xx.xx.xx.11:8443...
* TCP_NODELAY set
* Connected to api.privateserverdomaincantpublish.com (xx.xxx.xxx.11) port 8443 (#2)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /tmp/insomnia_7.1.1/2017-09-20.pem
* CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (OUT), TLS alert, handshake failure (552):
* error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small
* Closing connection 2

**Expected behavior**
Json response

**Desktop (please complete the following information):**
- OS: Centos 8
- Installation Method: rpm
- App Version 7.1.1
- OpenSSL 1.1.1

Contributor guide

Open the contributing guide

Research direction

Start with the reported reproduction steps and the libcurl/OpenSSL handshake log, especially the “dh key too small” failure on the CentOS 8 environment. Reproduce the request against the described IIS endpoint and identify the project entry point responsible for TLS connections; done means the request completes and returns the expected JSON response.

Written by the indexing model from the issue text.

Assessment

Domain
networking, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.