Fixing Errors When Importing Spexo Prebuilt Websites

Are you facing issues while importing a Spexo prebuilt website? The problem is likely related to server settings or resource limitations.

Since multiple factors can cause this issue, pinpointing the exact problem isn’t always straightforward. In this guide, we’ll go over the most common reasons behind import failures and provide solutions to resolve them.

Understanding the Importing Process #

All Spexo prebuilt websites are stored on our server. When you select a prebuilt website to import, Spexo establishes a connection with our server to fetch and transfer the necessary files to your website.

This process follows a structured flow, where your server sends a request to initiate the import, and our server responds by delivering the website data.

The connection request flow works as follows:

Before Importing Prebuilt Websites #

Before you import any of our available prebuilt websites, please make sure to check the Spexo Addons > System Info menu.

System Info – Check the System Info menu to ensure your server meets all requirements for a successful import. Settings that need attention are listed in red.

Common Issues During the Import Process #

Now that you understand how the Spexo prebuilt website import process works, let’s explore some common issues that may occur and how to fix them.

1) Blocked Requests Error During Import #

Error Description: #

The Blocked Requests Error occurs when the import process is interrupted because the server or firewall is blocking HTTP requests that are required to download or process certain resources. This can happen when the plugin tries to fetch external files (such as demo content, theme files, or images) from remote servers but is unable to due to security restrictions or server settings.

Possible Causes: #

1. Firewall or Security Plugin Restrictions: Some web hosting providers or security plugins may block external HTTP requests as part of their security measures.

2. Server-Side Blocks: Your server might be blocking external connections through HTTP or cURL, which is preventing the plugin from accessing the demo files.

3. DNS Issues: Sometimes, DNS settings on the server might cause the domain to be unreachable, preventing the plugin from importing external resources.

4. Outdated or Incorrect File Permissions: Incorrect file permissions on certain directories might block access to the necessary files during the import process.

Solution Steps: #

Step 1: Check Firewall and Security Plugin Settings #

• If you are using a firewall or security plugin (e.g., Wordfence, Sucuri, or similar), check the plugin’s settings to see if any requests from the server are being blocked.

• In most security plugins, you can find a Firewall or Blocking Logs section that shows blocked requests. Look for any entries related to cURL or external HTTP requests.

• You may need to whitelist specific domains or IP addresses that the plugin uses to fetch the demo content. These can typically be found in the plugin’s documentation or by contacting the plugin support.

Step 2: Disable ModSecurity (if enabled) #

• ModSecurity is a popular web application firewall used by many hosting providers. However, it may sometimes block legitimate requests during the import process.

• If your host allows it, temporarily disable ModSecurity and attempt the import again.

• To disable ModSecurity:

  • Log in to your hosting provider’s cPanel or server control panel.

  • Look for Security > ModSecurity and disable it temporarily.

  • If you’re unsure, contact your hosting provider for assistance with disabling ModSecurity.

Step 3: Check Server-Side cURL Settings #

• Ensure that cURL (the tool used for making HTTP requests) is enabled on your server.

• You can check this by creating a phpinfo.php file on your server with the following code:

  <?php phpinfo(); ?>

  • Look for the cURL section in the output. If it’s not enabled, you will need to enable it. Contact your hosting provider for assistance.

Step 4: Check File Permissions #

• Ensure the correct file permissions are set for the directories where the demo content is being imported.

  • For WordPress, typical permissions should be:

    • Folders: 755

    • Files: 644

  • If the permissions are incorrect, you can change them via FTP or cPanel File Manager.

2) WP_Error – cURL error 28: Operation Timed Out #

The cURL error 28 typically occurs when WordPress is unable to complete an HTTP request within the time limit. The error message usually looks like this.

This error is most commonly seen when importing a pre-built website, installing plugins, or fetching demo content. It indicates that the server timed out after waiting for 30 seconds (the default timeout) without receiving any response or data from an external server.

An error can appear in many places on your dashboard, such as on the Prebuilt Website page or the Prebuilt Block page. If you are using the Spexo Addons Pro version, the error might also occur during the License Key activation process.

WP_Error – cURL error 28: Operation timed out after 30001 milliseconds with 0 bytes received.

Possible Causes: #

1. Slow Server Response Time: The remote server hosting the demo content might be slow to respond, or there could be a temporary issue with the remote server.

2. Server Resource Limits: Your hosting server might be running low on resources (CPU, memory, etc.), which causes the cURL request to time out.

3. cURL Configuration: The cURL timeout settings on your server might be too short or improperly configured.

Solution Steps: #

Step 1: Increase PHP Limits and cURL Timeout #

• You can increase the max_execution_time and memory_limit in the php.ini file to allow longer running scripts and prevent timeouts.

  Update the following settings in your php.ini file:

max_execution_time = 300
memory_limit = 256M

• This will allow scripts to run for a longer period and increase memory allocation.
• Also, increase the cURL timeout in WordPress: You can add this snippet to your wp-config.php file:

define('WP_HTTP_CURL_TIMEOUT', 60); // Increase timeout to 60 seconds

3) 500 / 502 / Any 5XX Error #

5XX errors can occur due to various reasons, primarily related to server resource limitations or conflicts with installed plugins. If you encounter a 5XX error, follow these steps to troubleshoot:

• Check Installed Plugins – A faulty or incompatible plugin may be causing the issue. Try deactivating plugins one by one to identify the culprit.
• Review PHP Configuration – Ensure your server’s PHP settings meet Spexo’s recommended requirements. Increasing memory limits or execution time may help resolve the issue.
• Server Resources – If your hosting plan has limited resources, consider upgrading or optimizing your server for better performance.

For a detailed guide on resolving 500 – Internal Server Error, refer to this article.

4) XML File Storage Issue #

When importing a Spexo prebuilt website, WordPress needs to store an XML file in the /wp-content/ folder. If this process fails, it is often due to your hosting provider offloading the /wp-content/ folder to a third-party server or a misconfiguration in file permissions.

If this happens, you may see an error message like:

Looks like your host could not store XML file in /wp-content/ folder.

To resolve this issue, check your server settings or contact your hosting provider for assistance. For a detailed solution, please refer to this article.

Other Issues #

If your Spexo prebuilt website import process is interrupted for any reason not covered above, or if the suggested solutions do not resolve the issue, we recommend reaching out to our Support team by opening a Support ticket.

Keep in mind that most import-related issues are due to server configurations. Since our Support team cannot directly access your server settings, we will help identify the root cause and guide you on the necessary modifications. You may need to make these changes yourself or consult your hosting provider for further assistance.