Jose Celano

I guess we can implement what I did [here](https://github.com/josecelano/axum-server-timeout). That patch adds the timeout, but it does not send a 408 response to the client. Anyway, I think there is...

The `TimeoutAcceptor` I used to fix this issue does not work with TSL. See https://github.com/torrust/torrust-index/pull/584#issuecomment-2115499282. We have to remove it from the Axum server bootstrapping code for TSL, which means...

I've converted the discussion in the Axun repo into a issue: https://github.com/tokio-rs/axum/issues/2741

A [PR](https://github.com/hyperium/hyper/pull/3185) has been merged in the [hyper repo](https://github.com/hyperium/hyper/pull/3185). It changes the `http1_header_read_timeout` timeout.  This could fix this issue. We can try when this change is published in a...

> A [PR](https://github.com/hyperium/hyper/pull/3185) has been merged in the [hyper repo](https://github.com/hyperium/hyper/pull/3185). It changes the `http1_header_read_timeout` timeout. > >  > > This could fix this issue. We can try when this...

We are already using `hyper` 1.4.0 but it seems it does not solve the problem. We still need the custom TimeAcceptor which is only working when TSL is not enabled.

I've reopened the issue https://github.com/torrust/torrust-tracker/issues/324 to avoid duplicated comments on: - https://github.com/torrust/torrust-tracker/issues/612 - https://github.com/torrust/torrust-tracker/issues/613

Relates to: https://github.com/torrust/torrust-tracker/issues/567 @WarmBeer is working on [it](https://github.com/torrust/torrust-tracker/issues/567).

Hi @WarmBeer I've been thinking about this problem. I want to share some thoughts. ### Is the tracker actually crashing? The tracker was restarted on the demo environment but I...

I'm going to close this issue. I assume the tracker was restarted after the docker healthcheck. We could apply memory consumption limits in the future if we consider it useful...