# AWS beanstalk - Lost connection to server

**URL:** <https://discourse.nodered.org/t/aws-beanstalk-lost-connection-to-server/3313>\
**Category:** General\
**Created:** [20 September 2018 20:00 UTC](https://discourse.nodered.org/t/aws-beanstalk-lost-connection-to-server/3313 "2018-09-20T20:00:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![martin1](https://avatars.discourse-cdn.com/v4/letter/m/3be4f8/32.png) [@martin1](https://discourse.nodered.org/u/martin1)\
**Post date:** [20 September 2018 20:00 UTC](https://discourse.nodered.org/t/aws-beanstalk-lost-connection-to-server/3313/1 "2018-09-20T20:00:24Z")

</div>

Hi I have deployed node-red on amazon Elastic Beanstalk using [the tutorial](https://nodered.org/docs/platforms/aws#running-on-aws-ebs)and it works like a charm.

However I have one issue in the admin that keeps showing "Lost connection to server..." and keeps on trying to reconnect every minute. I don't mind so much but that for example it prevents me from seeing the debug output of a debug node, and this is starting to get difficult.

I have cleaned the cache to no avail. Stackoverflow questions with a similar issue have pointed to the fact that the admin server does cannot handle a websocket connection over https to the node-red backend [I suppose]. But I do not know how to change either my application's settings.js nor elastic beanstalk configuration to test any of this.

I am quite new to the whole AWS paradigms as well as node-red but not new to programming. Can somebody give me pointers to where I can go to gather the actual data that will help me debug the issue?

Many thanks,

Martin

---

<div class="post-metadata">

**Author:** ![kevingaasch](https://avatars.discourse-cdn.com/v4/letter/k/5fc32e/32.png) [@kevingaasch](https://discourse.nodered.org/u/kevingaasch)\
**Post date:** [25 April 2019 15:48 UTC](https://discourse.nodered.org/t/aws-beanstalk-lost-connection-to-server/3313/2 "2019-04-25T15:48:50Z")

</div>

did you figure this out? I am having the same issue

---

<div class="post-metadata">

**Author:** ![martin1](https://avatars.discourse-cdn.com/v4/letter/m/3be4f8/32.png) [@martin1](https://discourse.nodered.org/u/martin1)\
**Post date:** [26 April 2019 09:16 UTC](https://discourse.nodered.org/t/aws-beanstalk-lost-connection-to-server/3313/3 "2019-04-26T09:16:02Z")

</div>

Hi,

I think there are 3 options to solve this issue:

1. Difficult but cool: Stay with amazon and go look for some example settings files on how to allow not only TCP on port 80 but also redirecting other packets (I forgot their type) on another port (6000 or something) that manages the interface refresh. You will have to find the doc and test it on your own as I did not have time to do it myself.

2. Easier on IBM Cloud: 1 click deploy on IBM cloud service. Node-Red is “natively” supported by IBM cloud server.

3. Even easier SaaS: subscribe to [https://fred.sensetecnic.com](https://fred.sensetecnic.com).

Good luck!

---

<div class="post-metadata">

**Author:** ![guysqr](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/guysqr/32/11551_2.png) [@guysqr](https://discourse.nodered.org/u/guysqr)\
**Post date:** [29 August 2019 03:16 UTC](https://discourse.nodered.org/t/aws-beanstalk-lost-connection-to-server/3313/4 "2019-08-29T03:16:21Z")

</div>

Are you running more than one instance in EB? How are you logging into the admin UI? I suspect what is happening is that you have two instances and you keep switching between them, but you are only logged into one of them.

> **[guysqr/node-red-ha-on-aws](https://github.com/guysqr/node-red-ha-on-aws)**
>
> Node-RED on AWS with EFS. Contribute to guysqr/node-red-ha-on-aws development by creating an account on GitHub.

This gets around these issues by sharing the filesystem between instances using EFS, and using Auth0 for login. It's easy to set up. Try it and see how you go.