Erreur lors de l'assemblage des blocs - code d'état 504

Bonjour ,
J’ai bien entendu chercher ma réponse sur le Forum et partout sur le web mais vu le nombre de possibilité pour la même erreur, je n’ai pas réussi à trouver mon bonheur…

Le problème que je rencontre c’est d’avoir un message d’erreur “Erreur lors de l’assemblage des blocs, code d’état 504” (( Error when assembling chunks, status code 504 )) à la fin de l’envoi d’un gros fichier ( 7Gb ) pour le test (( 3Gb passe correctement ))
Je suis sur Docker, et je passe par un reverse proxy SWAG

Merci d’avance pour votre aide

nginx.conf

## Version 2023/04/13 - Changelog: https://github.com/linuxserver/docker-baseimage-alpine-nginx/commits/master/root/defaults/nginx/nginx.conf.sample

### Based on alpine defaults
# https://git.alpinelinux.org/aports/tree/main/nginx/nginx.conf?h=3.15-stable

user abc;

# Set number of worker processes automatically based on number of CPU cores.
include /config/nginx/worker_processes.conf;

# Enables the use of JIT for regular expressions to speed-up their processing.
pcre_jit on;

# Configures default error logger.
error_log /config/log/nginx/error.log;

# Includes files with directives to load dynamic modules.
include /etc/nginx/modules/*.conf;

# Include files with config snippets into the root context.
include /etc/nginx/conf.d/*.conf;

events {
    # The maximum number of simultaneous connections that can be opened by
    # a worker process.
    worker_connections 1024;
}

http {
    # Includes mapping of file name extensions to MIME types of responses
    # and defines the default type.
    include /etc/nginx/mime.types;
    default_type application/octet-stream;

    # Name servers used to resolve names of upstream servers into addresses.
    # It's also needed when using tcpsocket and udpsocket in Lua modules.
    #resolver 1.1.1.1 1.0.0.1 2606:4700:4700::1111 2606:4700:4700::1001;
    include /config/nginx/resolver.conf;

    # Don't tell nginx version to the clients. Default is 'on'.
    server_tokens off;

    # Specifies the maximum accepted body size of a client request, as
    # indicated by the request header Content-Length. If the stated content
    # length is greater than this size, then the client receives the HTTP
    # error code 413. Set to 0 to disable. Default is '1m'.
    client_max_body_size 0;

    # Sendfile copies data between one FD and other from within the kernel,
    # which is more efficient than read() + write(). Default is off.
    sendfile on;

    # Causes nginx to attempt to send its HTTP response head in one packet,
    # instead of using partial frames. Default is 'off'.
    tcp_nopush on;

    # all ssl related config moved to ssl.conf
    # included in server blocks where listen 443 is defined

    # Enable gzipping of responses.
    #gzip on;

    # Set the Vary HTTP header as defined in the RFC 2616. Default is 'off'.
    gzip_vary on;

    # Helper variable for proxying websockets.
    map $http_upgrade $connection_upgrade {
        default upgrade;
        '' close;
    }

    # Sets the path, format, and configuration for a buffered log write.
    access_log /config/log/nginx/access.log;

    # Includes virtual hosts configs.
    include /etc/nginx/http.d/*.conf;
    include /config/nginx/site-confs/*.conf;
}

daemon off;
pid /run/nginx.pid;

php-local.ini

; Edit this file to override php.ini directives

date.timezone = Europe/Paris
upload_max_filesize = 50G
post_max_size = 50G
max_input_time = 3600
max_execution_time = 3600

As-tu regardé tout simplement pour commencer les logs de Nextcloud ? pour voir ce qu’il dit quand le problème se pose ?
As-tu désactivé l’antivirus dans les apps Nextcloud ? Cela m’avait fait le même problème sur un NC client où le client avait activé cette app sans savoir comment elle fonctionnait !

Non pas pensé au log :upside_down_face:
( Non je n’ai pas mis d’App antivirus )

2023/08/13 11:12:37 [error] 371#371: *6187 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 78.126.225.***, server: _, request: "MOVE /remote.php/dav/uploads/sc62/web-file-upload-a6404c1d10ce4c0cfd2c8bd3c6cc5bfe-1691915941329/.file HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "nextcloud.xxx.fr"
2023/08/13 12:29:49 [error] 343#343: *2093 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 78.126.225.***, server: _, request: "MOVE /remote.php/dav/uploads/sc62/web-file-upload-0a9ce8322939e4107ba925fac5ce22d2-1691920278001/.file HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "nextcloud.xxx.fr"

merci et cela ressemble beaucoup à un time-out php ou web. As-tu vérifié la config PHP de ton serveur au niveau time-out et idem pour le serveur web (enfin les 2 car tu utilises un reverse proxy).
As-tu la possibilité d’essayer sans le reverse proxy ?

Après quelques recherche grâce au LOG
J’ai ajouté dans le fichier nginx.conf :


  # set timeouts
    proxy_connect_timeout 600s;
    proxy_send_timeout 600s;
    proxy_read_timeout 600s;
    fastcgi_send_timeout 600s;
    fastcgi_read_timeout 600s;

A priori ça l’air de fonctionner :smiley:
Merci de m’avoir mis sur une bonne piste !

1 Like