# Node Red running on AWS, no web socket connections
**URL:** https://discourse.nodered.org/t/node-red-running-on-aws-no-web-socket-connections/57738
**Category:** General
**Created:** [3 February 2022 18:15 UTC](https://discourse.nodered.org/t/node-red-running-on-aws-no-web-socket-connections/57738 "2022-02-03T18:15:30Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@eamonn.sullivan](https://discourse.nodered.org/u/eamonn.sullivan)
#### Post date: [3 February 2022 18:15 UTC](https://discourse.nodered.org/t/node-red-running-on-aws-no-web-socket-connections/57738/1 "2022-02-03T18:15:30Z")
I've managed to get a basic Node Red service (v2.2) running on an AWS EC2. It works -- as in I can create, deploy and use flows. However, there's a constant warning at the top: "Lost connection to the server. reconnecting in..." and the console shows that the connection to wss://.../comms failed.
I know I'm missing something basic here -- I'm using an express server, basically following the directions in [Running on Amazon Web Services : Node-RED](https://nodered.org/docs/getting-started/aws), with updated versions. Do I need to do something in the app.use() or something to open the websocket channel?
---
### Author:  [@eamonn.sullivan](https://discourse.nodered.org/u/eamonn.sullivan)
#### Post date: [3 February 2022 18:52 UTC](https://discourse.nodered.org/t/node-red-running-on-aws-no-web-socket-connections/57738/2 "2022-02-03T18:52:21Z")
I figured it out. Sorry for the bother. I needed to set up a proxypass:
```auto
+ ProxyPass /comms ws://localhost:${CLOUD_HTTPS_APP_PORT}/comms
+ ProxyPassReverse /comms ws://localhost:${CLOUD_HTTPS_APP_PORT}/comms
```
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [17 February 2022 18:52 UTC](https://discourse.nodered.org/t/node-red-running-on-aws-no-web-socket-connections/57738/3 "2022-02-17T18:52:58Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.