Artifact Statuses

Ready

Artifact is ready to be published

Cause: Artifact has been successfully generated and is ready to be published.

Published

 Artifact is live

Cause: Artifact has been published and is displayed publicly.

Warning

 Artifact is ready to be published but may require some attention.

Cause: Artifact may be published, but there may be some issues that may affect your site's performance or functionality. This status is most commonly seen when creating an artifact for a site that has active plugins or themes that use absolute URLs.
Solution: Please check your site for any themes or plugins that may be using absolute URLs, deactivate those themes or plugins, and generate a new artifact. If this process fails, please make a note of your site ID and contact support.

Failed

 We could not generate or deploy this artifact.

Cause: The generated artifact may not be published because an error has occurred during the artifact generation process
Solution: Please follow our Generator Troubleshooting guide. If those steps fail, please make a note of your site ID and contact support.

WordPress configurations

404: No posts or no pages are set as [Homepage] on Reading Settings.

Cause: An Artifact has been generated with incorrect [Homepage] settings or without any posts are published.
Solution: Update the [Homepage] settings on your site's WordPress Dashboard. 

500: Accessing WordPress is refused. Please check if JSON REST API is enabled on your site

Cause: Make sure JSON REST API is enabled.
Solution: Enable or unblock JSON REST API access on WordPress dashboard.

Accessing WordPress is refused. Please check to see if your site has been locked through authentication protection. (ex: Basic Authentication)

Cause: Shifter's generator was denied access to your WordPress site due to auth protection was enabled on your site.
Solution: Disable access protection settings or plugin on WordPress dashboard.

The content of index has been replaced by a plugin.

Cause: A plugin installed on your WordPress site has modified the index file on your site.
Solution: Disable any plugins that replaces content in your site's index file (e.g. Maintenance Mode, Under Construction)

 

Generator issue

Generating has been timed out. (Site id:<> is now generating.)

Cause: Generator has  timed out during site build.
Solution: Please make a note of your Site ID and Artifact ID along with the error message and contact support.

Site id:<> is now generating.

Cause: Another Artifact is currently generating.
Solution: Wait until the current artifact has finished generating. Then, click the [Generate] button to generate a new artifact.

timeout of 60000ms exceeded

Cause: Generator has  timed out during site build.
Solution: Please make a note of your Site ID and Artifact ID along with the error message and contact support.

WordPress site fail: CHANGE_PERMALINK_STRUCTURE

Cause: WordPress has taken too long to start up or to complete post processing.
Solution: This error is typically due to a high load on Shifter's backend infrastructure, or from loading too many files on WordPress. Wait for up to an hour. Then, restart WordPress and delete any unused and deactivated plugins or themes to reduce the size of your site. After this has been complete, generate a new artifact.

WordPress site fail: REPLACING_URLS

Cause: WordPress has taken too long to start up or to complete post processing.
Solution: This error is typically due to a high load on Shifter's backend infrastructure, or from loading too many files on WordPress. Wait for up to an hour. Then, restart WordPress and delete any unused and deactivated plugins or themes to reduce the size of your site. After this has been complete, generate a new artifact.

 

Docker or Server environment issue

The level of configured provisioned throughput for the table was exceeded. Consider increasing your provisioning level with the UpdateTable API.

Cause: Shifter has temporary reached capacity on our backend.
Solution: Contact us with attaching error message.

Object (s3://sys.status.getshifter/179d9489c9e744738b126b5e4f8af3b8) is not found.

Cause: WordPress couldn't start or is taking long time to start up or complete pre processing with WordPress.
Solution: Check your site's WordPress dashboard as well as your published site and check for any errors. If no there are no errors apparent please make a note of your site ID and artifact ID and contact support.

docker service failed (409):site <> is already running

Cause: There is currently another container  running for this site.
Solution: Reload the page or logout and log back in to the Shifter dashboard and check your site's status from the Shifter dashboard.

docker service failed (500):Error occurred during calls Backend Service.

Cause: Temporary backend high load.
Solution: Please wait and try again. If this error still occurs, please make a note of your site ID and error message and contact support.

statusCode: 401

Cause:  Authentication has failed due to WP JSON Rest API being disabled.
Solution: Enable WP JSON Rest API 

statusCode: 404

Cause:  There is no content to generate (no posts or pages).
Solution: This error is caused by attempting to generate an artifact from a site with no pots or contents. Publish one or more posts or pages and generate a new artifact.

connect ECONNREFUSED IP-ADDRESS:PORT-NUMBER

Cause: Failed to make HTTPS connection to docker.
Solution: Please wait and try again. If this error still occurs, please make a note of your site ID and error message and contact support.

not created

Cause:  There is no content to generate (no posts or pages).
Solution: This error is caused by attempting to generate an artifact from a site with no pots or contents. Publish one or more posts or pages and generate a new artifact.

Request failed with status code 500

Cause: Attempts to make connections to the Docker environment with HTTPS has failed.
Solution: Please wait and try again. If this error still occurs, please make a note of your site ID and error message and contact support.

Unexpected Error on transferring Theme or Plugin.

Cause: S3 syncing has timed-out.
Solution A: Reduce the amount of Generate after reducing files to transfer (delete unused or unnecessary plugins, themes, medias.
Solution B: Try to generate again after an interval.


 

Did this answer your question?