You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a while, the upload is then resumed and continues as expected. NetworkTimeoutError is still logged.
Upload finishes normally.
For many smaller files (~5Mb), this causes the upload to take a really long time.
Setup
OCIS set up with docker compose, following the ocis-full example but having stripped out anything but the core ocis functionality.
Using the Posix filesystem driver.
# have also tried setting the `Host` header with this directive
# then the origin does not match for auth
{
# servers :443 {
# trusted_proxies static 10.0.0.1/24
# }
# servers :80 {
# trusted_proxies static 10.0.0.1/24
# }
}
cloud.{$MY_DOMAIN} {
reverse_proxy ocis:9200 {
# header_up Host {upstream_hostport}
flush_interval -1
}
}
Additional context
Another point is that Caddy itself is behind a wireguard tunnel used to traverse a CGNAT, I am not sure if that might be part of the problem.
Describe the bug
I am getting slow uploads, especially for many smaller files.
Looking at the logs, it seems that the upload via tus does not work correctly.
Steps to reproduce
Behavior
The upload is initially normal for a few seconds but then stalls. Log is spammed with
After a while, the upload is then resumed and continues as expected.
NetworkTimeoutError
is still logged.Upload finishes normally.
For many smaller files (~5Mb), this causes the upload to take a really long time.
Setup
OCIS set up with docker compose, following the ocis-full example but having stripped out anything but the core ocis functionality.
Using the Posix filesystem driver.
Replaced Traefik reverse proxy with Caddy, followed the guide from tus on how to configure proxies
OCIS:
docker-compose.yaml
.env
Caddy:
Caddyfile
Additional context
Another point is that Caddy itself is behind a wireguard tunnel used to traverse a CGNAT, I am not sure if that might be part of the problem.
Relevant OCIS logs:
Full OCIS log
Caddy Access Log
The text was updated successfully, but these errors were encountered: