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

[brazeiro63]

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

[guimephiles]

hey, same issue here

[vkruoso]

The default docker-compose file does not work correctly mainly due to this issue. Anyway, the main API image has the manager within itself, and can be enabled by setting the env variable SERVER_DISABLE_MANAGER=false.

[IntezMercurio]

I still have the same problem. Has there been any update on this?