# How to see kong logs of kong-ingress-controller

**URL:** <https://discuss.konghq.com/t/how-to-see-kong-logs-of-kong-ingress-controller/4526>\
**Category:** General\
**Created:** [September 30, 2019, 9:21am UTC](https://discuss.konghq.com/t/how-to-see-kong-logs-of-kong-ingress-controller/4526 "2019-09-30T09:21:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dangtrinhnt](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/dangtrinhnt/32/1356_2.png) [@dangtrinhnt](https://discuss.konghq.com/u/dangtrinhnt)\
**Post date:** [September 30, 2019, 9:21am UTC](https://discuss.konghq.com/t/how-to-see-kong-logs-of-kong-ingress-controller/4526/1 "2019-09-30T09:21:47Z")

</div>

Hi,

I deployed kong-ingress-controller and trying to run the `getting started` guide on an AWS EKS cluster. I got this error when trying to access the $PROXY\_IP/foo address:

> HTTP/1.1 502 Bad Gateway  
> Date: Mon, 30 Sep 2019 09:19:21 GMT  
> Content-Type: text/plain; charset=UTF-8  
> Transfer-Encoding: chunked  
> Connection: keep-alive  
> Server: kong/1.3.0  
> X-Kong-Upstream-Latency: 2  
> X-Kong-Proxy-Latency: 7  
> Via: kong/1.3.0
> 
> An invalid response was received from the upstream server

I would want to check the kong logs to see what happens but couldn’t access the ingress controller’s shell. The only logs that I can get are via `kubectl logs ingress-kong-pod-name ingress-controller -n kong` which has no useful information.

If you know a way to troubleshoot this, please let me know.

Many thanks,

---

<div class="post-metadata">

**Author:** ![dangtrinhnt](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/dangtrinhnt/32/1356_2.png) [@dangtrinhnt](https://discuss.konghq.com/u/dangtrinhnt)\
**Post date:** [September 30, 2019, 10:06am UTC](https://discuss.konghq.com/t/how-to-see-kong-logs-of-kong-ingress-controller/4526/2 "2019-09-30T10:06:39Z")

</div>

Okie, I now can see the logs of kong by going into the kong ingress containers:

kubectl exec -it ingress-kong-xxx -n kong – /bin/ash

---

<div class="post-metadata">

**Author:** ![eshepelyuk](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/eshepelyuk/32/164_2.png) [@eshepelyuk](https://discuss.konghq.com/u/eshepelyuk)\
**Post date:** [October 4, 2019, 5:46pm UTC](https://discuss.konghq.com/t/how-to-see-kong-logs-of-kong-ingress-controller/4526/3 "2019-10-04T17:46:16Z")

</div>

```
$ kubectl get pods | grep ingress
ingress-kong-845cfb4996-xnzg7 2/2 Running 1 62m

```

1. To see logs of proxy (kong instance itself)

2. To see logs of ingress controller

---

<div class="post-metadata">

**Author:** ![dangtrinhnt](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/dangtrinhnt/32/1356_2.png) [@dangtrinhnt](https://discuss.konghq.com/u/dangtrinhnt)\
**Post date:** [October 8, 2019, 1:13am UTC](https://discuss.konghq.com/t/how-to-see-kong-logs-of-kong-ingress-controller/4526/4 "2019-10-08T01:13:26Z")

</div>

Thanks for the suggestion.