Evolution Manager container starts but Cloudflare returns 502 Bad Gateway

[VOVALDOAPI]

Welcome!

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

What did you do?

Evolution API version: 2.3.7

Manager image: atendai/evolution-manager

Docker Compose

OS: Ubuntu 24.04

Reverse proxy: Cloudflare

Domain: api.odinfood.com.br

Description

I deployed Evolution API using Docker Compose along with PostgreSQL, Redis, and Evolution Manager. All containers start successfully and appear healthy according to docker ps.

However, when accessing the manager through my domain (https://api.odinfood.com.br/manager/), Cloudflare returns a 502 Bad Gateway error.

Cloudflare reports that the host is failing, even though the containers are running.

Docker Status

Output of docker ps:

evolution_manager atendai/evolution-manager Up
evolution_api evoapicloud/evolution-api Up
evolution_postgres postgres:15-alpine Up
evolution_redis redis:7-alpine Restarting

Note: Redis is restarting repeatedly.

Observed Issues

Redis container enters a restart loop.

Manager container starts but may not be reachable externally.

Cloudflare returns:

Error 502
Host Error

Expected Behavior

The Evolution Manager panel should be accessible at:

https://api.odinfood.com.br/manager/

or directly via server IP:

http://SERVER_IP:4444

docker-compose.yml

services:

evolution_api:
image: evoapicloud/evolution-api:v2.3.7
container_name: evolution_api
restart: always
ports:
- "8080:8080"
environment:
SERVER_URL: https://api.odinfood.com.br
AUTHENTICATION_TYPE: apikey
AUTHENTICATION_API_KEY: EvoKey_98xKzPq2
DATABASE_ENABLED: "true"
DATABASE_PROVIDER: postgresql
DATABASE_CONNECTION_URI: postgresql://postgres:EvoDB_44zXq1@postgres:5432/evolution
CACHE_REDIS_ENABLED: "true"
CACHE_REDIS_URI: redis://redis:6379/1
depends_on:
- postgres
- redis

evolution_manager:
image: atendai/evolution-manager
container_name: evolution_manager
restart: always
ports:
- "4444:4444"
environment:
- EVOLUTION_API_URL=http://evolution_api:8080
depends_on:
- evolution_api

postgres:
image: postgres:15-alpine
container_name: evolution_postgres
restart: always
environment:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: EvoDB_44zXq1
POSTGRES_DB: evolution

redis:
image: redis:7-alpine
container_name: evolution_redis
restart: always

Additional Information

Docker network was created successfully.

All containers start, but Redis repeatedly restarts.

Cloudflare proxy is enabled for the domain.

Direct access via domain results in 502 error.

Questions

Is the atendai/evolution-manager image still maintained?

Is there an official Docker image for Evolution Manager compatible with Evolution API 2.3.7?

Could the Redis restart loop cause the manager or API to fail behind Cloudflare?

Any help or clarification would be appreciated.

What did you expect?

Questions

Is the atendai/evolution-manager image still maintained?

Is there an official Docker image for Evolution Manager compatible with Evolution API 2.3.7?

Could the Redis restart loop cause the manager or API to fail behind Cloudflare?

What did you observe instead of what you expected?

Questions

Is the atendai/evolution-manager image still maintained?

Is there an official Docker image for Evolution Manager compatible with Evolution API 2.3.7?

Could the Redis restart loop cause the manager or API to fail behind Cloudflare?

Screenshots/Videos

No response

Which version of the API are you using?

V2.3.7

What is your environment?

Windows

Other environment specifications

4gb ram
ubunto 24.4 LTS

If applicable, paste the log output

No response

Additional Notes

No response

[Alexandre200-lab]

Este arquivo já contém as correções do Redis e a inclusão do Nginx Proxy Manager para eliminar o Erro 502 do Cloudflare.

version: '3.8'

services:

Banco de Dados - Persistência para Evolution

evolution_postgres:
image: postgres:15-alpine
container_name: evolution_postgres
restart: always
environment:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: EvoDB_44zXq1
POSTGRES_DB: evolution
volumes:
- ./data/postgres:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U postgres"]
interval: 5s
timeout: 5s
retries: 5
networks:
- evolution_network

Cache - Corrigido loop de reinicialização

evolution_redis:
image: redis:7-alpine
container_name: evolution_redis
restart: always
command: redis-server --appendonly yes
volumes:
- ./data/redis:/data
healthcheck:
test: ["CMD", "redis-cli", "ping"]
interval: 5s
timeout: 3s
retries: 5
networks:
- evolution_network

Evolution API v2.3.7

evolution_api:
image: evoapicloud/evolution-api:v2.3.7
container_name: evolution_api
restart: always
environment:
- SERVER_URL=https://api.odinfood.com.br
- AUTH_TYPE=apikey
- AUTH_API_KEY=EvoKey_98xKzPq2
- DATABASE_ENABLED=true
- DATABASE_PROVIDER=postgresql
- DATABASE_CONNECTION_URI=postgresql://postgres:EvoDB_44zXq1@evolution_postgres:5432/evolution
- CACHE_REDIS_ENABLED=true
- CACHE_REDIS_URI=redis://evolution_redis:6379/1
depends_on:
evolution_postgres:
condition: service_healthy
evolution_redis:
condition: service_healthy
networks:
- evolution_network

Nginx Proxy Manager - Resolve o Erro 502 e gerencia SSL

nginx_proxy_manager:
image: 'jc21/nginx-proxy-manager:latest'
container_name: nginx_proxy_manager
restart: always
ports:
- '80:80' # HTTP
- '443:443' # HTTPS
- '81:81' # Painel Admin
volumes:
- ./data/nginx/config:/data
- ./data/nginx/letsencrypt:/etc/letsencrypt
networks:
- evolution_network

networks:
evolution_network:
driver: bridge`