# Logs and Shell Disconnected

**URL:** <https://forums.suse.com/t/logs-and-shell-disconnected/7752>\
**Category:** Rancher 1.x\
**Created:** [November 7, 2017, 2:28pm UTC](https://forums.suse.com/t/logs-and-shell-disconnected/7752 "2017-11-07T14:28:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lhull](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/lhull/32/2631_2.png) [@lhull](https://forums.suse.com/u/lhull)\
**Post date:** [November 7, 2017, 2:28pm UTC](https://forums.suse.com/t/logs-and-shell-disconnected/7752/1 "2017-11-07T14:28:19Z")

</div>

My logs and shell have not worked in a long time now… when I look at log or shell, it immediately disconnects

Using Rancher v1.6.10, all of my hosts are Docker v17.06.2-ce, tried downgrading docker, each version does not work.

All servers have ntp installed, so it isn’t a time issue, even verified the time on all servers, they are all identical

I also have all ports open (privately) between the hosts

---

<div class="post-metadata">

**Author:** ![superseb](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/superseb/32/2424_2.png) [@superseb](https://forums.suse.com/u/superseb)\
**Post date:** [November 8, 2017, 11:00am UTC](https://forums.suse.com/t/logs-and-shell-disconnected/7752/2 "2017-11-08T11:00:07Z")

</div>

Best way to debug this is using Developer Tools and seeing what happens to the request. If you can share a screenshot or the copied request/response, we can take a look.

---

<div class="post-metadata">

**Author:** ![lhull](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/lhull/32/2631_2.png) [@lhull](https://forums.suse.com/u/lhull)\
**Post date:** [November 8, 2017, 12:03pm UTC](https://forums.suse.com/t/logs-and-shell-disconnected/7752/3 "2017-11-08T12:03:24Z")

</div>

This is what the response is showing…

[https://rancher.exzeo.com/v2-beta/projects/1a1281/containers/1i26623/?action=logs](https://rancher.exzeo.com/v2-beta/projects/1a1281/containers/1i26623/?action=logs)

request:  
{follow: true, lines: 500}

response:  
`{"id":null,"type":"hostAccess","links":{},"baseType":"hostAccess","actionLinks":{},"token":"eyJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJjYXR0bGUiLCJob3N0VXVpZCI6ImM5NzYzODI5LWY5NTMtNGZlNy01NTM0LWQyM2RiZTBmOWE5ZiIsImtpZCI6ImRlZmF1bHQiLCJpc3MiOiJodHRwOlwvXC9jYXR0bGUuaW8iLCJleHAiOjE1MTAxNDIyMjUsImxvZ3MiOnsiQ29udGFpbmVyIjoiZGYyZTQ3YWRhYThlYzMxMjhmMGZjYWZmZTU0YjI3MGM5YzU4N2ZiMTIyMDE0YTQ4ZTQ0M2FkYTYwY2QwMDk1MSIsIkxpbmVzIjo1MDAsIkZvbGxvdyI6dHJ1ZX0sImlhdCI6MTUxMDE0MTkyNX0.Krzq654LanLs4CFHOhWYIpAburAuqt4D3Y2l4Vk5AUBOlowbyWnqbHKSLyAk6wRAZjV12as83qoGaOkEU3YzvwUsP8r5ZcIwJqMmcN0ytJoobbkQx6VlvztWa8APG6QSWc54mzpcZ9poXCgZKkqPDjII77-f2heFkFdFyUdh4SAaZI6aRuIce-P2wCp4YHsV4dc_cESYjfAMzLjJsxdcNS8aOYJwkqUD63BNcnDldMkMYrIAELE9MhT_hvXF0B2EW6soUTWtFe82WMWTZP9DZCu48fVKIq4aAvSo48ZXmV4n77L5O2LkD2mF-GqnJs1ElPjR8Wqz83KFFR7Jfsw2FA","url":"wss:\/\/rancher.exzeo.com\/v1\/logs\/"}`

wss://rancher.exzeo.com/v1/logs/?token= is getting a 404, I wonder if its the load balancer I’m using in AWS, I’m using an Application Load Balancer