# Websocket issue with exec - no stdout response

**URL:** <https://discuss.kubernetes.io/t/websocket-issue-with-exec-no-stdout-response/10694>\
**Category:** General Discussions\
**Created:** [April 29, 2020, 5:05pm UTC](https://discuss.kubernetes.io/t/websocket-issue-with-exec-no-stdout-response/10694 "2020-04-29T17:05:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![marc.boorshtein](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/marc.boorshtein/32/915_2.png) [@marc.boorshtein](https://discuss.kubernetes.io/u/marc.boorshtein)\
**Post date:** [April 29, 2020, 5:05pm UTC](https://discuss.kubernetes.io/t/websocket-issue-with-exec-no-stdout-response/10694/1 "2020-04-29T17:05:26Z")

</div>

building a go client to run commands against a pod using websockets. I’m able to connect, authorize and upgrade with the url `wss://192.168.2.144:6443/api/v1/namespaces/openunison/pods/openunison-orchestra-78858c5f4-8bnkb/exec?command=echo+%27test%27&stdin=false&stdout=true&sterr=true` but while trying to receive a `TextMessage` i just get an error `websocket: close 1000 (normal)` using gorilla as the websockets library. Am I missing something? i’d expect a response of `test` back (or some kind of error?).

Thanks