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

Curl error when requesting API #4639

Open
Sh4d1 opened this issue Feb 1, 2018 · 9 comments
Open

Curl error when requesting API #4639

Sh4d1 opened this issue Feb 1, 2018 · 9 comments
Labels
kind/bug A bug in existing code (including security flaws) topic/gateway Topic gateway

Comments

@Sh4d1
Copy link

Sh4d1 commented Feb 1, 2018

Version information:

go-ipfs version: 0.4.13-3b16b74
Repo version: 6
System version: amd64/linux
Golang version: go1.9.2

Type:

Bug

Description:

Hey!

I have an issue, I'm not sure it is directly related to go-ipfs though. Anyway, I'm running the Docker image on ipfs.ptrk.io. When I do curl http://ipfs.ptrk.io:5001/api/v0/version it is all good. However when I run curl https://ipfs.ptrk.io/api/v0/version I get the wanted output but curl is still waiting (ie, I don't get the shell back). After about 1min, I get curl: (56) Unexpected EOF.
When I try on the browser, I get the result but the page is still loading.

Also, running curl http://ipfs.ptrk.io:5001/api/v0/version --http1.1 works normally. I guess there is some problem with http2 but I'm not sure if the issue is with Traefik or go-ipfs.

Feel free to ask for more information :)

Cheers!

@whyrusleeping
Copy link
Member

interesting... this feels like a bug.

@whyrusleeping whyrusleeping added kind/bug A bug in existing code (including security flaws) topic/gateway Topic gateway labels Feb 3, 2018
@worph
Copy link

worph commented May 24, 2018

For information I also got this error on go-ipfs version: 0.4.15 and I also use Traefik

@kliu128
Copy link

kliu128 commented Jul 18, 2018

I am also getting this error, using Traefik.

@whyrusleeping
Copy link
Member

@Pneumaticat What is your setup? Do you have a gateway running on a server with nginx? How are you reproducing the issue?

@kliu128
Copy link

kliu128 commented Jul 18, 2018

Initially, I had Traefik reverse-proxying port 5001 to IPFS daemon's port 5001, doing TLS termination as well. This created the situation where HTTP 1.1 worked fine, but HTTP 2 hung for approximately 3 minutes.

I then switched to a nginx reverse proxy of 5001 (again doing TLS termination), which seems to work fine with both HTTP 1 and 2. This might be a traefik bug, then.

@Stebalien
Copy link
Member

Or a go http bug. We've run across several, unfortunately.

@nicolashardy
Copy link

Does anyone has some workaround for this one ? :(

@pierreh37
Copy link

I solved this issue by using ngingx reverse proxy instead of traefik and now this is working so I don't think it is linked to goipfs but maybe an issue with traefik.

@Stebalien
Copy link
Member

May be #5168.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) topic/gateway Topic gateway
Projects
None yet
Development

No branches or pull requests

7 participants