Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

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

An invalid response was received from the upstream server #3314

Closed
omerkarabacak opened this issue Mar 19, 2018 · 7 comments
Closed

An invalid response was received from the upstream server #3314

omerkarabacak opened this issue Mar 19, 2018 · 7 comments
Labels
task/needs-investigation Requires investigation and reproduction before classifying it as a bug or not.

Comments

@omerkarabacak
Copy link

omerkarabacak commented Mar 19, 2018

Summary

We have problem while running Kong in our Docker Swarm cluster. We have one upstream, one upstream target and one api.

After a while, when we send a request to kong api endpoint we get this response from "An invalid response was received from the upstream server"

This generally happens at first request.

Additional Details & Logs

  • Kong version 0.12.1
  • Kong error logs
2018/03/19 08:39:11 [error] 49#0: *18910 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.255.0.2, server: kong, request: "POST /one-time-password-service/v2/password HTTP/1.1", upstream: "http://x.x.x.x:y/v2/password", host: "a.b.c:8090"
  • Operating System
    CoreOS 1688.3.0 (Beta Channel)
    docker version
    Server:
    Engine:
    Version: 17.12.1-ce
    API version: 1.35 (minimum version 1.12)
    Go version: go1.9.4
    Git commit: 7390fc6
    Built: Tue Feb 27 22:10:31 2018
    OS/Arch: linux/amd64
    Experimental: true
@bungle bungle added the task/needs-investigation Requires investigation and reproduction before classifying it as a bug or not. label Mar 19, 2018
@thibaultcha
Copy link
Member

Hi,

There is little we can do to help you here, this is an issue between Nginx and your upstream server that is behaving wrongly. See this topic to help you debug the issue. Thanks

@mgiangrandi
Copy link

Hi, any news about this issue? Same problem here...

@wmrodrigues
Copy link

Same problem as well, anyone had any progress?

@thibaultcha
Copy link
Member

@mgiangrandi @wmrodrigues As explained in the topic I linked to in my previous comment, this is not a problem with Kong, but likely a misconfiguration of the upstream server. The topic has a list of steps to follow to help you troubleshoot the issue.

@wmrodrigues
Copy link

I'm reading the topic right now, thanks for the tips @thibaultcha

@jerneyio
Copy link

jerneyio commented Sep 11, 2018

I'd like to add that I was receiving this message today because of a misconfiguration of a service on the Kong side (my error). My service was as follows (notice the incorrect HTTP port):

{
  "host": "host.com",
  "created_at": 1536606408,
  "connect_timeout": 60000,
  "id": "a53cef5b-46f5-4fc4-b70c-6d20a2fbcd76",
  "protocol": "http",
  "name": "mock-service",
  "read_timeout": 60000,
  "port": 443,
  "path": "/api",
  "updated_at": 1536697486,
  "retries": 5,
  "write_timeout": 60000
}

When I switched the port to 80, things started working correctly again.

@inallib
Copy link

inallib commented Dec 6, 2022

take a look at here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task/needs-investigation Requires investigation and reproduction before classifying it as a bug or not.
Projects
None yet
Development

No branches or pull requests

7 participants