question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Request timing out in 60 seconds regardless of timeout-keep-alive value

See original GitHub issue

Hello, I’m running uvicorn server with Quart, and when I try to upload a large file or one through a slow shared folder connection, the request always times out at 60 seconds.

I’m not running any other server like NGINX, the response is coming from Uvicorn itself

This is how I’m running it :

uvicorn.run('app:application', host="0.0.0.0", port=500, loop="asyncio", reload=True, workers=2, timeout_keep_alive=3600, log_level='debug')

It returns me 408 Request Timeout after 60s in the server logs.

Funny thing is the browser is not notified immediately, only after it finished “uploading” the whole file he’s aware of the timeout, not sure that’s just normal

Using uvicorn 0.11.5

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:9 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
euri10commented, Jul 20, 2020
0reactions
euri10commented, Jul 20, 2020

you cannot send a reload signal, reload is automatically triggered once a watched file is modified, it’s more a development mode feature.

Yes I understand it’s for development

I just wanted to know if there’s a documented way of safely restarting the server in production, or do I just use a supervisor and restart the process?

Not that I know, I think most people use gunicorn for that

Read more comments on GitHub >

github_iconTop Results From Across the Web

TCP Keepalive Best Practices - detecting network drops and ...
Send TCP Keepalives successfully (within 15 minutes), before idle socket timeout (typically 60 or 30 minutes). Make sure TCP Keepalives retry at ...
Read more >
MQTT Keep Alive Interval Explained With Examples
The default keep alive period for the Python MQTT client is 60 secs, but it can be set to anything you want when...
Read more >
Configure Read Timeout and Keep-Alive Timeout values for ...
The default keep-alive idle timeout value is 5 seconds, but you can now configure a higher value up to 60 seconds.
Read more >
How to increase Apache's timeout correctly when mod_proxy ...
HTTP 408 is "Request Timeout". It occurs when the client connects but doesn't send any data before the timeout triggers.
Read more >
Add/Allow Specification of tcp_keepalive timers #848 - GitHub
I'm trying to enable/set TCP Keepalive 'tickles" every 60 seconds to keep the proxy connection from timing out.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found