# Client network socket disconnected before secure TLS connection was established
**URL:** https://discourse.nodered.org/t/client-network-socket-disconnected-before-secure-tls-connection-was-established/69581
**Category:** General
**Created:** [25 October 2022 15:47 UTC](https://discourse.nodered.org/t/client-network-socket-disconnected-before-secure-tls-connection-was-established/69581 "2022-10-25T15:47:40Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@fabiobeoni](https://discourse.nodered.org/u/fabiobeoni)
#### Post date: [25 October 2022 15:47 UTC](https://discourse.nodered.org/t/client-network-socket-disconnected-before-secure-tls-connection-was-established/69581/1 "2022-10-25T15:47:41Z")
Hi,
I am experiencing the error message _Client network socket disconnected before secure TLS connection was established_, when I open the Editor UI (okay) and I click on "Sign In" button (error).
I run nodered as follow:
1. protected by Keycloack (Auth, both Editor UI and HTTP endpoints)
2. docker container
3. hosted on aws ec2 instance, with a load balancer on top owning the ssl certificate.
So the ssl certificate is on top of the ec2/docker/nodered and transparent for them...
In nodered, the `settings.js` section related to ssl is commented out like this:
```auto
//https: {
// key: fs.readFileSync('privatekey.pem'),
// cert: fs.readFileSync('certificate.pem')
//},
```
I don't get where the error message comes form... no output in logs.
More over, I had a look to this repo (node-red on aws) linked from the nodered ufficial docs: [GitHub - guysqr/node-red-ha-on-aws: Node-RED on AWS with EFS to enable horizontal scaling. Uses Elastic Beanstalk to create additional instances into a load-balanced auto-scaling group as required.](https://github.com/guysqr/node-red-ha-on-aws) and I see the `settings.js` there pretty similar to mine... ssl commented out.
Any suggestion is very appreciated.
Thanks, F.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [25 October 2022 16:40 UTC](https://discourse.nodered.org/t/client-network-socket-disconnected-before-secure-tls-connection-was-established/69581/2 "2022-10-25T16:40:26Z")
Can I just check, are your clients connecting via http or https?
---
### Author:  [@fabiobeoni](https://discourse.nodered.org/u/fabiobeoni)
#### Post date: [27 October 2022 06:47 UTC](https://discourse.nodered.org/t/client-network-socket-disconnected-before-secure-tls-connection-was-established/69581/3 "2022-10-27T06:47:19Z")
By https...
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [27 October 2022 08:09 UTC](https://discourse.nodered.org/t/client-network-socket-disconnected-before-secure-tls-connection-was-established/69581/4 "2022-10-27T08:09:22Z")
OK, so AWS is terminating the TLS and I wonder if it is configured to handle websocket comms?
Whatever proxy your AWS config is using needs to be configured to handle websockets which requires http 1.1
---
### Author:  [@fabiobeoni](https://discourse.nodered.org/u/fabiobeoni)
#### Post date: [27 October 2022 17:29 UTC](https://discourse.nodered.org/t/client-network-socket-disconnected-before-secure-tls-connection-was-established/69581/5 "2022-10-27T17:29:58Z")
Yes, websocket is allowed.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [27 October 2022 18:46 UTC](https://discourse.nodered.org/t/client-network-socket-disconnected-before-secure-tls-connection-was-established/69581/6 "2022-10-27T18:46:19Z")
I think you will find that it is misconfigured.
You will need something that captures and shows the handshake. You might be able to use the network tab on your browser or you might be better trying something like CURL with -v.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [26 December 2022 18:46 UTC](https://discourse.nodered.org/t/client-network-socket-disconnected-before-secure-tls-connection-was-established/69581/7 "2022-12-26T18:46:34Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.