Error: unhandled courier request error: unknown error

[gnuhpc]

ES 2.3.3 Kibana 4.5.1

One Django-based proxy (revproxy) was used ahead of kibana.

The kibana can be reached via the proxy, but got the error as below:

Oops!

Looks like something went wrong. Refreshing may do the trick.

or clear your session
Fatal Error
Courier Fetch Error: unhandled courier request error: unknown error

Version: 4.5.1
Build: 9892

Error: unhandled courier request error: unknown error
handleError@http://192.168.145.128:8000/bundles/kibana.bundle.js?v=9892:78902:23
AbstractReqProvider/AbstractReq.prototype.handleFailure@http://192.168.145.128:8000/bundles/kibana.bundle.js?v=9892:78822:15
callClient/</<@http://192.168.145.128:8000/bundles/kibana.bundle.js?v=9892:78716:14
callClient/<@http://192.168.145.128:8000/bundles/kibana.bundle.js?v=9892:78714:10
processQueue@http://192.168.145.128:8000/bundles/commons.bundle.js?v=9892:42360:29
scheduleProcessQueue/<@http://192.168.145.128:8000/bundles/commons.bundle.js?v=9892:42376:28
$RootScopeProvider/this.$get</Scope.prototype.$eval@http://192.168.145.128:8000/bundles/commons.bundle.js?v=9892:43604:17
$RootScopeProvider/this.$get</Scope.prototype.$digest@http://192.168.145.128:8000/bundles/commons.bundle.js?v=9892:43415:16
$RootScopeProvider/this.$get</Scope.prototype.$apply@http://192.168.145.128:8000/bundles/commons.bundle.js?v=9892:43712:14
done@http://192.168.145.128:8000/bundles/commons.bundle.js?v=9892:38161:37
completeRequest@http://192.168.145.128:8000/bundles/commons.bundle.js?v=9892:38359:8
createHttpBackend/</requestError@http://192.168.145.128:8000/bundles/commons.bundle.js?v=9892:38310:10

Please give a hint for me, Thanks.

[gnuhpc]

Without the proxy ,kibana works just like a charm. I am wondering why a http proxy can make such a mess...

[Bargs]

Hi @gnuhpc, please ask support questions like this in our discussion forums: https://discuss.elastic.co/c/kibana. We reserve Github issues for confirmed bugs and feature requests.

This is a pretty common issue, so I'd search the discussion forums for pre-existing issues on this topic. Most likely your proxy is stripping out request params, headers, or perhaps forwarding to the wrong URL.

[gnuhpc]

Thank you, I will check the related threads there.

[gnuhpc]

@Bargs BTW, I checked them all but no clue there, I am wondering this is a common issue. Can you provide a link for me? Thx

[Bargs]

I can't say for sure that anyone has experienced your exact issue, but proxies are a source of a lot of problems in general: https://discuss.elastic.co/search?q=proxy%20category%3A7

Feel free to post a new topic as well if none of those help.