By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account Click the page button again，it will work.

Additional Details

• Kong version (0.30-enterprise-edition)
• Using Kong docker image through AWS ECS

Kong log:

2018/11/14 08:33:28 [error] 61#0: *23791 upstream prematurely closed connection while reading response header from upstream, client: 10.191.18.44, server: kong, request: \"GET /backend/api/xxxx HTTP/1.1\", upstream: \"https://<ipaddress>:xxx/api/xx”, host: “xxxxx”, referrer: “xxxxxx”

When I access backend api directly, It works without problem.

give me a help please.
thanks.

The error is not from Kong itself, but indicates that Kong cannot communicate properly with your upstream service. See a similar issue at #3785 , and since this error is Nginx-specific, you'll also be able to find a plethora of resources online explaining this error and how you can identify the cause/resolve it.

Left a comment at #3785 with some more details on how you could debug this and possibly resolve it :)

This isn't a Kong issue per-say, but I am not closing this issue only because depending on the root cause, it may be that we would want to expose ways to tweak the nginx proxy module configuration... or not. I'd like to know what the root cause was once you find out.