Firstly, please ensure you have followed our guides for publishing, found here:
- WordPress: https://d.pr/VEiD8F
- Drupal: https://d.pr/JBmnfS
1) Standard troubleshooting steps
1. Check if the CMS token from Instapage, for the workspace you are publishing from, is added in the Settings tab in the WordPress or Drupal plugin. You can get the CMS token by clicking on the name of your workspace on the top left, then Workspace settings > Integrations, as shown in the GIF below.
2. In the Settings tab of the Instapage plugin in WordPress/Drupal, under the CMS tokens, verify that the checkbox next to Legacy Support is unchecked. It must be turned off in order for everything to work correctly.
3. Make sure that your Instapage plugin is up to date.
4. At the bottom of the same Settings tab, check that all of the specifications are in green and if they are not, make the necessary changes.
5. Separate from our plugin, there is a settings section on the left side of your WordPress where you can find the category Permalinks. They must be set to post name in order for you to be able to publish your Instapage pages.
6. Flush the cache from the entire website or disable plugins that could cause caching, as that can cause our pages not to update correctly.
7. When you are looking to unpublish a page, unpublish it from Instapage first, then go into the plugin and delete the URL from the list. Both steps are necessary for the page to be unpublished. If the second step is not done, when the page is pushed to be republished again, it will not show up in the Add Page tab.
2) Access denied / Request failed with status 500
If you are encountering an Access denied or Request failed with status 500 error when attempting to publish, it means that the subdomain+domain of your website are not associated with the Instapage account you are publishing from. This error can also appear in the form of There was an error during page update process.
To remedy this, you will need to add the subdomain+domain in Instapage as if you were using Custom Domain / CNAME publishing first. To do that, follow these steps linked here: https://d.pr/easwKu.
! You must add the exact subdomain you use for WordPress/Drupal publishing, not a different subdomain of the same domain. If you have your main website on www.domain.com and you are publishing on that, add "www.domain.com", not "pages.domain.com" or anything else.
When you are prompted with the message from the image below, click on Request Access.
The domain owner will receive an email with your request as well as a notification in the Domain Access section of their account. If they approve it, you will then be able to publish your page on WordPress/Drupal normally after the approval.
You only need to add the domain+subdomain to the list. Do not create a CNAME record as instructed at the end of the domain adding process, as that will take your website down. The CNAME instructions only refer to custom domain publishing, and it is not a necessary step if you are adding the domain here for WordPress/Drupal publishing.
If you know that you own this domain and you would like us to move it to your account, please follow this guide: https://d.pr/Cb6NKe.
This is a security measure put in place to prevent non-authorized accounts from using your domain. Don't worry if you see the SSL pending message. It is normal not to have an SSL certificate provided by Instapage for this subdomain since you have your main WordPress website on it, and we only enable SSL certificates for CNAME records that point to our server address. In the case of WordPress publishing, the SSL is added on the WordPress end and it will not show up in the Instapage domains list.
Root/naked domain publishing
If the WordPress/Drupal website is not using a subdomain (keep in mind "www" is also a subdomain) but is published on the root domain (domain.com instead of www.domain.com or pages.domain.com, etc), then only the Instapage account that is listed as the owner can publish on it. If another Instapage account has domain access granted to it by the owner, it can use subdomains of that domain, but not the root domain.
If you are in the latter situation, please ask the domain owner to send us a request at help@instapage.com that mentions they want to allow you to publish on the root domain. The request must come from the email address associated with their paid account and must include your email address and the domain in the message.
3) cURL error 28
cURL is a PHP library. The cURL error 28 means that your site tried to perform a request using the cURL library but the specified timeout period was reached before getting a successful result for the request. The plugin makes cURL requests to our server (pageserve.co) in order to publish new pages, update existing ones and run functionalities such as form submissions, integrations, and more.
You can check the PHP version by following these steps: WordPress -> Tools -> Site Health -> Info -> Server -> Check PHP and cURL version.
To use PHP’s cURL functions, you must install the libcurl package. PHP requires libcurl version 7.10.5 or later. As of PHP 7.3.0, version 7.15.5 or later is required. As of PHP 8.0.0, version 7.29.0 or later is required.
- Check your PHP version
php -version - Install the same-version PHP-cURL:
sudo apt install php7.4-curl(or the version that you have) - Restart the server.
If you need any further help with troubleshooting WordPress or Drupal publishing, you can reach out to our Support Team at help@instapage.com or on live chat support whose working hours can be found here: https://d.pr/FMDeHa.
4) UTM Parameters Stripping
If you notice that UTM parameters or lead data are not being captured correctly, please check the following:
Managed hosts like WP Engine or Pantheon often strip UTM parameters to optimize performance. Ensure your hosting settings allow for these query strings.
If you are using one of these systems, navigate to the Instapage plugin > Settings tab. Scroll down and ensure the Custom experiences option is enabled.
Caching Plugins: Active WordPress caching plugins (e.g., W3 Total Cache, WP Rocket) can interfere with page scripts. Try clearing your cache or temporarily disabling the plugin to test lead capture.