# unable to access in AWS

**URL:** <https://forum.ansible.com/t/unable-to-access-in-aws/32512>\
**Category:** AWX Project\
**Tags:** windows, aws\
**Created:** [March 23, 2020, 12:51pm UTC](https://forum.ansible.com/t/unable-to-access-in-aws/32512 "2020-03-23T12:51:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matthew\_Wimpelberg](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@Matthew\_Wimpelberg](https://forum.ansible.com/u/Matthew_Wimpelberg)\
**Post date:** [March 23, 2020, 12:51pm UTC](https://forum.ansible.com/t/unable-to-access-in-aws/32512/1 "2020-03-23T12:51:39Z")

</div>

I’ve been able to identify this as an nginx issue.

{“log”:“2020/03/23 12:51:22 [error] 133#0: \*23 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.16.172.31, server: \_, request: "GET /websocket/ HTTP/1.1", upstream: "[http://127.0.0.1:8051/websocket/\](http://127.0.0.1:8051/websocket/%5C)”, host: "172.16.175.197"\n",“stream”:“stderr”,“time”:“2020-03-23T12:51:22.684174535Z”}  
{“log”:“172.16.172.31 - - [23/Mar/2020:12:51:22 +0000] "GET /websocket/ HTTP/1.1" 504 578 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36" "-"\n”,“stream”:“stdout”,“time”:“2020-03-23T12:51:22.684298239Z”}