Subsequent requests hang for exactly 1 minute #36
Comments
|
hey @mysterybear, could you run the client in verbose mode and share logs |
|
Here we go: The first request went through very quickly, I hit the return carriage in stdout before the subsequent request and then after the request was made, can see between 18:35:41 and 18:36:41, a 1 minute time for the request to complete |
|
are these HTTP requests or is it some kind of a persistent protocol? |
|
Thanks for the quick response! HTTP with TLS, I'm hitting Here is the log from the ktunnel server pod: Same pattern, I added some comments, same pattern, first request fine, made a change to the HTML being served by my local HTTP server and made a new request, and you're right, it's precisely 1 minute that the subsequent request takes. I was doing this with a Next.js app before, but now I just changed to a simple barebone HTML hello world served with https://github.com/svenstaro/miniserve just to confirm there isn't any funny business going on with this, and there isn't I don't think, exactly the same behaviour Thanks again, let me know anything else I can do, very happy to conduct further tests, more logs, etc Edit: forgot to include client log for the above server session, though am pretty sure it's the same pattern as in previous post, but can't hurt. |
mysterybear
changed the title
|
it seems that the 60 seconds are derived from the client (not the ktunnel client, the one that is trying to reach the server over the tunnel), which client are you using to make the requests? |
|
@mysterybear is this issue still relevant? |
|
@omrikiei Hi, I was using curl as the client, sorry, got caught up with Xmas/NYE! The problem was also apparent when just using my browser (Chromium) as a client also I am in the middle of a migration from one cloud provider to another right now though, I guess it will be interesting to see if the problem is still happening on the new provider. Could keep this open for a few days and I can get back after that, or close and I can re-open if still an issue? Up to you, thanks for your time! |
|
Hey @mysterybear, no problem keeping this open.. Happy new year 👍 |
|
Cheers @omrikiei I have tried again and am still getting the same behaviour, whether I use curl or the browser as the client, and whether I use miniserve or Next.js as the server. Usually the first request goes through right away though, but then if I make a change, it's always that next request that hangs for 1 minute. Can you think of any other tests I can try to find out what's going on, or any other suggestions? Thanks again! |
|
Ah I figured I can post from my ingress logs (grep'd for "error"), I'll just put |
|
less noisy version with just a single index.html served using miniserve: (the logs in the previous example were tunnelling a full Next.js site) |
omrikiei
pushed a commit
that referenced
this issue
Jan 9, 2021
|
Hi @mysterybear, I authored a new beta version that closes the connection from the client on EOF - I think this is what caused the connection to hang... |
|
@omrikiei Hey this is working wonderfully now, tyvm! One thing though, I did have to run the client with |
|
@mysterybear thank you again for your feedback, fixed versioning tags issue as well and released v1.3.3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey,
I've got it set up and it works, but the request/response round-trip is intermittently very, very slow, or hangs and doesn't complete.
I have no idea what kinds of logs/tests to try to give more meaningful information about this issue, if there are any suggestions I'd be happy to undertake them.
Cheers!
The text was updated successfully, but these errors were encountered: