[Bug]: Invalid parameter must-revalidate in gzip_proxied directive (nginx.conf line 11)

Abierto Apto para principiantes
  • ¿Algo no está bien?
#18 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
docker, nginx
Área
devops, infrastructure

Línea de trabajo

Abre nginx.conf e inspecciona la línea 11 de la sección «Gzip compression». Elimina el parámetro no compatible gzip_proxied, valida después la configuración y confirma que el contenedor evolution_frontend se inicia sin el error de Nginx indicado.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Prerequisites
  • I have searched existing issues to ensure this bug hasn't been reported before
  • I have read the documentation
  • I am using a supported version of Evolution Manager
Bug Description

Description

There is an invalid configuration value in the nginx.conf file under the “Gzip compression” section. On line 11 the directive gzip_proxied currently includes must-revalidate as one of its parameters:

However, according to the official Nginx documentation for the gzip_proxied directive, the valid values are:
off, expired, no-cache, no-store, private, no_last_modified, no_etag, auth, any. :contentReference[oaicite:1]{index=1}
The value must-revalidate is not listed and thus causes the error observed:

Impact

  • Nginx fails to start or becomes stuck in the “Starting” state due to this invalid directive, preventing proper compression and serving of content.
  • Compression behaviour may not apply as intended for proxied responses, which may affect performance or caching behaviour.
  • It introduces configuration drift and potential confusion, since must-revalidate is a valid HTTP Cache-Control directive but not valid in the context of gzip_proxied.

Suggested Fix

To fix this issue, the must-revalidate parameter should be removed from the gzip_proxied directive. For example, update line 11 to something like:

Steps to Reproduce
  1. Pull or build the evolution-api stack, which uses evolution-manager-v2 and the evolution_frontend container.
  2. Deploy it via Docker (for example docker run, docker compose up, or similar).
  3. The evolution_frontend container attempts to start.
  4. In its logs you see an error like:
    invalid value "must-revalidate" in /etc/nginx/conf.d/nginx.conf:11
  5. Because of this invalid directive in nginx.conf (line 11) the Nginx process fails to start properly and the container stays in a Starting or Crash / Restart state instead of reaching Running.
Expected Behavior

Container evolution_frontend shoould start.

Actual Behavior

Because of this invalid directive in nginx.conf (line 11) the Nginx process fails to start properly and the container stays in a Starting or Crash / Restart state instead of reaching Running.

Screenshots

No response

Browser

Chrome

Browser Version

141.0.7390.123

Evolution Manager Version

v2.0.0

Evolution API Version

latest

Operating System

Windows

Console Logs
2025-11-02 11:27:32


Starting Evolution Manager v2...
2025-11-02 11:27:36 Starting Evolution Manager v2...
2025-11-02 11:27:25 
2025/11/02 14:27:25 [emerg] 6#6: invalid value "must-revalidate" in /etc/nginx/conf.d/nginx.conf:11
2025-11-02 11:27:25 nginx: [emerg] invalid value "must-revalidate" in /etc/nginx/conf.d/nginx.conf:11
2025-11-02 11:27:26 2025/11/02 14:27:26 [emerg] 7#7: invalid value "must-revalidate" in /etc/nginx/conf.d/nginx.conf:11


nginx: [emerg] invalid value "must-revalidate" in /etc/nginx/conf.d/nginx.conf:11
2025-11-02 11:27:27


2025/11/02 14:27:27 [emerg] 6#6: invalid value "must-revalidate" in /etc/nginx/conf.d/nginx.conf:11
2025-11-02 11:27:27


nginx: [emerg] invalid value "must-revalidate" in /etc/nginx/conf.d/nginx.conf:11
Additional Context

No response

Contribution
  • I would like to work on fixing this bug
Lenguaje dominante
TypeScript
Estrellas
20
Forks
42
Sin PR fusionados en 30 d

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de evolution-foundation/evolution-manager-v2

Todos los issues de evolution-foundation/evolution-manager-v2

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.