evolution_frontend container loop issue invalid value "must-revalidate" in nginx.conf:

[mmojadad]

Welcome!

• Yes, I have searched for similar issues on GitHub and found none.

What did you do?

After install version 2.3.5 container evolution_frontend can not start .
Starting Evolution Manager v2...
[emerg] 6#6: invalid value "must-revalidate" in /etc/nginx/conf.d/nginx.conf:11

What did you expect?

Start normally

What did you observe instead of what you expected?

Starting Evolution Manager v2...
[emerg] 6#6: invalid value "must-revalidate" in /etc/nginx/conf.d/nginx.conf:11

Screenshots/Videos

No response

Which version of the API are you using?

2.3.5

What is your environment?

Windows

Other environment specifications

No response

If applicable, paste the log output

No response

Additional Notes

No response

[joaocps]

+1

[gbpufscar]

+1 Me too

[DaniloGouvea]

I've created a pull request that solves this issue (EvolutionAPI/evolution-manager-v2#17) but I'm new here and not sure how often the maintainers review and approve these things.

I have a workaround in the meantime: you can create a local copy of the the file evolution-manager-v2/.docker/nginx.conf, and change the line 11 from
gzip_proxied expired no-cache no-store private must-revalidate auth
to
gzip_proxied expired no-cache no-store private auth;

Then, in the docker-composer.yaml, in the frontend service, you add the line
volumes:
- ./nginx.conf:/etc/nginx/conf.d/nginx.conf:ro

It should enable the frontend container to start.

[zaryabmustafa]

Experiencing the same issue on a brand new install

[luisadidomenico]

Same problem here.

[maikramer]

Pessoal, aqui tem um workaround descomplicado que é só adicionar ao compose, e ser feliz

    image: evoapicloud/evolution-manager:latest
    entrypoint: /bin/sh
    command: >
      -c "
      if [ -f /etc/nginx/conf.d/nginx.conf ]; then
        sed -i 's/ must-revalidate//g' /etc/nginx/conf.d/nginx.conf;
      fi &&
      nginx -g 'daemon off;'
      "