Mauricio Siu af16250561 fix(wordpress): route loopback requests through Traefik to fix cURL error 28 ...

WordPress resolves its own public domain to the server's public IP from
inside the container, so REST API / WP-Cron / Site Health loopback
requests depend on hairpin NAT, which times out (cURL error 28) on many
hosts. Pin the site domain to the dokploy-traefik container IP in
/etc/hosts at startup (with retries, since Traefik joins the compose
network shortly after the container starts) so loopback traffic stays
inside the Docker network for both HTTP and HTTPS. No-op fallback when
dokploy-traefik is not resolvable.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-14 11:55:19 -06:00

..

docker-compose.yml

fix(wordpress): route loopback requests through Traefik to fix cURL error 28

2026-07-14 11:55:19 -06:00

meta.json

feat: per-template metadata — eliminate meta.json merge conflicts

2026-07-07 23:58:10 -06:00

template.toml

fix(wordpress): route loopback requests through Traefik to fix cURL error 28

2026-07-14 11:55:19 -06:00

wordpress.png

feat: Add extensive collection of application blueprints with Docker Compose configurations

2025-03-09 23:36:58 -06:00