Not all URLs are published to S3

  • Hi there,

    We’re testing WP2Static on a larger website. The initial crawl list contains 469428 URLs. The deployment appears to only be partially successful to S3. It stops suddenly around line 1524 (46kb into the 20MB crawl list).

    Any ideas what we can do find the cause? Happy to provide any additional info needed.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter nekranox

    (@nekranox)

    Forgot to include that we have tried both via web and via WP-CLI. We also cleared the deploy cache.

    CLI output:

    [xxxxxx@xxxxxxxxx xxxxxxxx]$ wp wp2static deploy
Deploying static site via: s3
Success: Deployed to: s3 in 01:04:34

    The time indication above is confusing because it looks like 1 hour 4 minutes but it actually took around 1 minute to complete.

    • This reply was modified 4 years, 10 months ago by nekranox.
    Plugin Author Leon Stafford

    (@leonstafford)

    Hi @nekranox – could you please try the following:

    export as a ZIP and use AWS’s CLI tool to sync the unzipped directory to S3?

    If that works as expected, we can back-track and find out at which point it’s failing.

    Cheers,

    Leon

    Thread Starter nekranox

    (@nekranox)

    Hi there @leonstafford

    I generated the ZIP, it took 33 minutes and had even less content than is in the S3 bucket. Only 50 folders instead of 110.

    It looks like its the html generation process that is failing. How can we investigate this further?

    Thanks

    • This reply was modified 4 years, 9 months ago by nekranox.
    Plugin Author Leon Stafford

    (@leonstafford)

    Hi @nekranox,

    Please shoot me an email (can find via the main website) and we can continue the investigation.

    Cheers,

    Leon

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Not all URLs are published to S3’ is closed to new replies.

Tags