3.0 - Server dislikes our behavior, excessive load detected.

[marcel-wiechmann]

Setup:

• Server: 4.0-rc1 & 4.0-rc2
• Client 1: ArchLinux/3.0.1 - Build from Source (AUR)
• Client 2: macOS/3.0.2
• Client 3: Windows/3.0.2 (Unaffected)
• Proxy: nginx

With the new client, I encounter the problem that the synchronization stops and I receive the error “Server dislikes our behavior, excessive load detected.” Which seems to be related to QT (https://codebrowser.dev/qt5/qtbase/src/network/access/http2/http2protocol.cpp.html).

I’m using the recommend settings from https://docs.opencloud.eu/docs/admin/getting-started/container/docker-compose/external-proxy.

The issue doesn’t occur with the 2.0 client (Linux/AppImage)

Within the nginx and container logs, I was unable to find any specific error message related to the issue (default log level).

Windows: I'm unable to reproduce the issue with the Windows Client. I've made the folder (6.500 Files / 65 GB), that I've used for testing, offline available and everything went fine. Under Linux and macOS the process has to be restarted every few minutes.

[TheOneRing]

With 3.0 we finally enabled http2 support, so a different behaviour is expected.

Is this issue a duplicate of #733 ?

[marcel-wiechmann]

@TheOneRing It's not a duplicate of the issue. Here the problem is that the new client seems to cause too many requests that the server cancels the connection, at least that's the error message that I receive on Linux and macOS while Windows is unaffected.

[TheOneRing]

Server dislikes our behavior, excessive load detected. means http code 420, which sounds related to the nginx config issue.

[TheOneRing]

Please provide client and server logs.

[rhafer]

Within the nginx and container logs, I was unable to find any specific error message related to the issue (default log level).

It might make sense to increase the log-level of the nginx proxy and the opencloud proxy service to get some more information about what is going on. To increase the opencloud proxy service's log level just set PROXY_LOG_LEVEL=debug.
(For nginx please consult the nginx documentation)

[zumlernen-de]

I think the issue affects the windows client as well. Just not as fast as on the Linux client. If I click "Always keep on this device" on the right click menu on a space folder in the Windows Explorer I get the same error after a while.

We have a new Installation (4.0rc2) with the default nginx setup shown in the installation guide.

Edit: It seems to be some kind of rate limit / ddos protection issue, as I'm able to sync fine when I limit the Download speed to e.g. ~4000KB/s (not tested the limits yet). Our usual download speed would be between 20000-40000KB/s.

Edit2: Setting the Download Speed to 9999KB/s (the maximum I'm able to set it to in the Client) fixes the issue as well. I'm not sure which setting is responsible for this behaviour in Nginx, but we should set it to something to support Fiber-Connection speeds.

[DennisGruendig]

I have the same issue, my installation is running behind an nginx reverse proxy and I have tried all the recommended custom settings but it doesn't change the broken client behaviour. When I download huge files over the web interface, everything is working fine.

[TheOneRing]

Please provide Nginx and client http logs. https://docs.opencloud.eu/docs/user/desktop-client/common-functionality/logging

[marcel-wiechmann]

Sorry @TheOneRing, it took a while but here's the requested details:

nginx Configuration

server {
    server_name cloud.example.tld;

    http2 on;
    client_max_body_size 300M;

    location / {
        proxy_pass http://127.0.0.1:9200;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
    }

    # Disable buffering - essential for SSE
    proxy_buffering off;
    proxy_request_buffering off;

    # Prevent nginx from trying other upstreams
    proxy_next_upstream off;

    # Extend timeouts for long connections
    proxy_read_timeout 3600s;
    proxy_send_timeout 3600s;
    keepalive_requests 100000;
    keepalive_timeout 1m;
    http2_max_concurrent_streams 512;

    error_log /var/log/nginx/opencloud_error.log debug;
    access_log /var/log/nginx/opencloud_access.log combined;

    listen [::]:443 ssl; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/cloud.example.tld/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/cloud.example.tld/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = cloud.example.tld) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    server_name cloud.example.tld;

    listen [::]:80;
    listen 80;
    return 404; # managed by Certbot


}

Logfiles (I hope I removed all private details).

opencloud_error.log

opencloud_access.log

OpenCloud.tar.gz

[bitkris-dev]

Suddenly having the same issue out of the blue, I've updated to 3.0 weeks ago btw, not now.

In my case it's not even dependent on the size. I have this error on 2 mp4 files: one of 566 MB and one of 87 MB, but I have synced way bigger files (>2GB) with no issues, even this same day, so I don't get what's happening.

The files are present both in my OpenCloud space and in my hard disk, but somehow tries to sync them and returns the "Server dislikes our behaviour, excessive load detected" for those 2 files.

I'm also getting at the same time an error on a file which was already present, synced months ago and wasn't touched at all now:

"Problemi ,File ,Cartella ,Dimensione,Account ,Tempo ,Stato ,
Error transferring https://.com/dav/spaces///20250610_234729.jpg - server replied: ,/20250610_234729.jpg ,,4,4 MB,bitkris@,2025-12-16T02:35:51.000,Messaggio ,
"

Earlier I was also getting force disconnected from the client, every space was apparently offline as soon as these errors popped out, and returned online when restarting OpenCloud, then re-creating the issue after some seconds, in a loop.

Even considering a possible bug on network configuration, I honestly don't get why it's planned to give it a so extreme reaction to a normal usage.

Fixed it by removing the files manually from both my computer and the OpenCloud space, then reuploading them from an external source via frontend and re-downloading to my computer via client sync. But now I have an orphaned file which I can't delete from OpenCloud, can't find any documentation on how to clean it.

[umrath]

Same problem here.
Restricting the upload speed to 9999, even 5000 is not sufficient for me, still ends up in the same problem.

I try to run now with 4000 until a fix is available.

The bug is easily reproducible for me because I'm currently uploading quite some data and it happens quite soon after restarting the client.

macOS v3.0.3
server 4.0.0 on Debian/Proxmox behind an Nginx Proxy Manager

Update: Setting the limit to 4000 and even 2500 does not help.
I'm trying to play around with massively increased timeout settings for the Nginx Proxy Manager now.
They were previously set to an already generous 3600s. I have changed it to 43200s now.

[TheOneRing]

@marcel-wiechmann thx for the logs. However, http logs were not enabled in the client logs it would be great if someone could upload client logs with http logging enabled.

[TheOneRing]

@marcel-wiechmann what is the reason you set proxy_http_version .