Artifact Status
- Ready: The artifact is ready for publication.
- Cause: The artifact was generated successfully and is ready for publication.
- Published: The artifact has been published.
- Reason: The artifact has been published and is available to the public.
- Warning: The artifact is ready for publication, but caution may be required.
- Cause: The artifact can be published, but there may be some issues that could affect site performance or functionality. This status is commonly seen when creating artifacts for sites that have active plugins or themes using absolute URLs.
- Solution: Check for any themes or plugins on your site that may be using absolute URLs, disable those themes or plugins, and then generate a new artifact. If this process fails, make a note of your site ID and contact support.
- Failure: This artifact could not be generated or deployed.
- Cause: An error occurred during the artifact generation process, so the generated artifact may not be publishable.
- Solution: Follow the generator troubleshooting guide. If these steps fail, please note your site ID and contact support.
WordPress Settings
- 404: The post or page is not set as the [Homepage] in the Display Settings.
- Cause: The artifact was generated with an incorrect [Homepage] setting, or the post has not been published.
- Solution: Update the [Homepage] setting in your site’s WordPress dashboard.
- 500: Access to WordPress was denied. Please check if the JSON REST API is enabled on your site.
- Cause: Please verify that the JSON REST API is enabled.
- Solution: Enable or unblock JSON REST API access in your WordPress dashboard.
- Access to WordPress was denied. Please check whether the site is locked by authentication protection (e.g., Basic Authentication).
- Cause: The Shifter generator was denied access to the WordPress site because authentication protection is enabled on the site.
- Solution: Please disable the access protection settings or plugins in the WordPress dashboard.
- The contents of the index file have been overwritten by a plugin.
- Cause: A plugin installed on your WordPress site has modified the site’s index file.
- Solution: Disable any plugins that replace the contents of your site’s index file (e.g., Maintenance Mode, Under Construction).
Generator Issues
- Generation timed out. (Site ID: <> is currently being generated.)
- Cause: The generator timed out while building the site.
- Solution: Make a note of the Site ID, Artifact ID, and error message, then contact support.
- Site ID: <> is currently being generated.
- Cause: Another artifact is currently being generated.
- Solution: Please wait until the current artifact has finished generating. Then, click the [Generate] button to generate a new artifact.
- timeout of 60000ms exceeded
- Cause: The generator timed out while building the site.
- Solution: Make a note of the Site ID, Artifact ID, and error message, then contact support.
- WordPress site fail: CHANGE_PERMALINK_STRUCTURE
- Cause: WordPress is taking too long to start up or complete post processing.
- Solution: This error typically occurs due to high load on Shifter’s backend infrastructure or too many files being loaded into WordPress. Please wait up to one hour. Next, restart WordPress and remove unused and deactivated plugins or themes to reduce the size of your site. Once this is complete, generate a new artifact.
- WordPress site fail: REPLACING_URLS
- Cause: WordPress is taking too long to start up or complete post processing.
- Solution: This error typically occurs because of high load on Shifter’s backend infrastructure or because there are too many files being loaded into WordPress. Please wait up to one hour. Next, restart WordPress and remove unused and deactivated plugins or themes to reduce the size of your site. Once this is complete, generate a new artifact.
Docker or Server Environment Issues
- The level of configured provisioned throughput for the table was exceeded. Consider increasing your provisioning level using the UpdateTable API.
- Cause: There is a temporary capacity shortage in Shifter’s backend.
- Solution: Please contact us and include the error message.
- Object (s3://sys.status.getshifter/179d9489c9e744738b126b5e4f8af3b8) is not found.
- Cause: WordPress cannot start, or it is taking a long time to start or complete preprocessing.
- Solution: Check the site’s WordPress dashboard and the live site for any errors. If you do not find any errors, note the site ID and artifact ID, and contact support.
- docker service failed (409): site <> is already running
- Cause: Another container is currently running for this site.
- Solution: Reload the page, or log out of the Shifter dashboard and log back in, then check the site’s status from the Shifter dashboard.
- docker service failed (500): Error occurred during calls to the Backend Service.
- Cause: Temporary high load on the backend.
- Solution: Please wait a moment and try again. If this error persists, please note down the site ID and error message, and contact support.
- statusCode: 401
- Cause: Authentication failed because the WP JSON REST API is disabled.
- Solution: Enable the WP JSON REST API.
- statusCode: 404
- Cause: There is no content to generate (no posts or static pages).
- Solution: This error occurs when attempting to generate an artifact from a site with no posts or content. Publish at least one post or static page, then generate a new artifact.
- connect ECONNREFUSED IP-ADDRESS:PORT-NUMBER
- Cause: The HTTPS connection to Docker failed.
- Solution: Please wait a moment and try again. If this error persists, please note your site ID and the error message, then contact support.
- not created
- Cause: There is no content to generate (no posts or pages).
- Solution: This error occurs when attempting to generate an artifact from a site with no posts or content. Please publish one or more posts or static pages and generate a new artifact.
- Request failed with status code 500
- Cause: An attempt to connect to the Docker environment using HTTPS failed.
- Solution: Please wait a moment and try again. If this error persists, please note your site ID and the error message, then contact support.
- Unexpected Error while transferring a Theme or Plugin.
- Cause: The S3 synchronization timed out.
- Solution:
- Solution A: Reduce the number of files to be transferred (by deleting unused or unnecessary plugins, themes, and media), then lower the generation volume.
- Solution B: Wait a while, then try generating again.