Skip to content

WordPress Template : REST API and Loopback Requests Failing due to cURL timeout (Error 28) #1788

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
thepiyushchandwani opened this issue Apr 27, 2025 · 0 comments

Comments

@thepiyushchandwani
Copy link

thepiyushchandwani commented Apr 27, 2025

To Reproduce

  1. Deploy a WordPress site using the default WordPress Install Template on Dokploy.
  2. Complete the deployment without modifying any isolation or network settings.
  3. Visit WordPress Admin → Tools → Site Health.

You will find two major errors :

  • REST API is not working :
    (http_request_failed) cURL error 28: Connection timed out after 10000 milliseconds

  • Loopback request failed :
    cURL error 28: Connection timed out after 10000 milliseconds

Current vs. Expected behavior

Current Behavior:
After following the steps above, REST API endpoints fail to respond, and loopback requests timeout, breaking several WordPress features such as the Block Editor, scheduled cron jobs, and plugin/theme management.

Expected Behavior:
REST API endpoints and loopback requests should work immediately after a clean deployment without manual intervention, ensuring full functionality of WordPress.

Image

Provide environment information

Operating System : Ubuntu 24.04.2 LTS x86_64
Dokploy : v0.21.8
What application are you trying to deploy : Wordpress

Which area(s) are affected? (Select all that apply)

Docker Compose, Traefik, Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

The site is accessible, but internal cURL requests fail, which seems related to networking setup in the template.

Will you send a PR to fix it?

No

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant