Simply static is stalled

  • Resolved elfrasquito

    (@elfrasquito)


    5 months ago

    hello

    I’m using simply static to create a static copy of my website but it stalls. After setting it up as per guidelines, half an hour later the plugin still runs but nothing seems to happen. I can see the log only if I download the txt file. Nothing is printed otherwise. Here is the log

    [2026-01-08 13:42:48] [class-ss-archive-creation-job.php:128] Starting a job; no job is presently running
    [2026-01-08 13:42:48] [class-ss-archive-creation-job.php:129] Here’s our task list: setup, fetch_urls, create_zip_archive, wrapup
    [2026-01-08 13:42:48] [class-ss-archive-creation-job.php:147] Pushing first task to queue: setup
    [2026-01-08 13:42:48] [class-ss-background-process.php:201] Saving to key: wp_archive_creation_job_batch_b7f253ff6022d53867d13ed20ed865de. Data: Array( [0] => setup)

    I’m using simply static 3.5.4.

    If I cancel the export and run another one the job lasts a few seconds. The log says

    [2026-01-08 14:29:31] [class-ss-archive-creation-job.php:160] Not starting; we’re already in the middle of a job

    Everything on the diagnostics has a green tick.

    Can you help me with this? thanks


Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author patrickposner

    (@patrickposner)

    4 months, 3 weeks ago

    Hey @elfrasquito,

    this could have a few reasons that you can look into:

    • is WP-Cron up and running?
    • Is the installation running in a Docker container?
    • Is Basic Auth set up for the site but the credentials are missing in the settings?
    • Any incompatible plugins that might block the execution?

    I would also take a look into the WP Debug log – there might be an error here explaining it.

    James Joseph Finn

    (@jamesjosephfinn)

    3 months, 3 weeks ago

    For anyone running WordPress Docker in a Coolify setup, my experience has been that extra_hosts in the compose file should not map the site url to the container IP, but instead to host-gateway, e.g.:

    services:
      wordpress:
        extra_hosts:
          - 'wp.example.com:host-gateway'

    Attempting to use the container’s docker network IP did not work for me. host-gateway works fine.

    @patrickposner what do you think about this? It works for me!

    Plugin Author patrickposner

    (@patrickposner)

    3 months, 3 weeks ago

    @jamesjosephfinn agreed – that’s the way to go!

    It kinda depends on how the Docker image is structured (on DO, for example, you have to map it to the container’s IP address), but using the host-gateway is generally the better approach.

    I really wish we wouldn’t even need to talk about these things in 2026, but here we are, wp_remote_get still not using the right host automatically..

    I’ll add a note referencing this ticket, and we put that in the docs!

    James Joseph Finn

    (@jamesjosephfinn)

    3 months, 3 weeks ago

    @patrickposner you are a gentleman, and a scholar!

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

Tags