WP STAGING is a high-quality enterprise-level backup and staging software for WordPress and works on most available hosting providers and servers. WP STAGING runs over 1000 automated tests before every release to ensure it always works as expected.
If your hosting provider is not listed here, it just means that we have not tested the plugin for that provider. Therefore, the chances that WP STAGING will work on your hosting system are still excellent.
- 1 WP STAGING Verified & Compatible Hosting Providers
- 2 WP STAGING Incompatible Hosting Providers
- 3 Are You a Hosting Provider and Like to be Listed Here?
WP STAGING Verified & Compatible Hosting Providers
Limitations: There a few Strato server, that have a 4GB maximum allowed file size limit. If your website is bigger than 4GB and you want to use the WP Staging backup feature, you will need to split the backups file size into smaller chunks. You can use this filter to do so.
WordPress.com – Backup, Restore and Migration
We will soon support the backup and migration of staging sites created on the wordpress.com platform.
Due to technical restriction and limitations of the wordpress.com hosting platform, it will not be possible to create a staging site with WP STAGING on the same system in a subfolder. However, you can create a blank WordPress site on another server and then use WP STAGING and its award-winning backup feature to migrate the data to that other site.
WP STAGING Incompatible Hosting Providers
WP STAGING does not work with the following hosting providers due to server restrictions and less powerful systems.
Few known hosting providers are incompatible with WP Staging, leading to a bad experience.
Aruba still has some servers with Microsoft Windows Server 2012 R2 Standard. WP STAGING does not run on them due to file restrictions Aruba.it is set on the root folder of the WordPress website. We don’t recommend using a website with such an old webserver.
The hosting provider, aruba.it does not support staging sites created by WP Staging (date 14th, June 2020). As a result, the staging site throws an error 500, and the WordPress debug log is ignored and not written on their systems, making it impossible for us to debug the issues.
Update August 8, 2022: Staging Site and backup creation with WP STAGING now works on Aruba.it.
We experienced on a client site in Aruba.it that the WordPress `siteurl` in the database always returned a wrong scheme, http instead of https, even though the siteurl seemed to correct with https in the database. To solve this and to return the correct prefixed siteurl with http we had to update the siteurl again with the same value in the database.
We don’t know what caused that issue, but it could be caused by an unclean database caching setting or some aruba.it custom redirects for http links.
It is also noticeable that searching through the database for http://example.com was impossible, and the search term was immediately replaced with https://example.com. This indicates that this is a database internal redirect of HTTP > HTTPS.
IONOS 1&1 Web Hosting (Limited with some plans)
Some IONOS hosting packages execute WordPress in a closed environment with the user/group 43:600. That seems to be a preconfigured WordPress installation, probably made by a one-click installation script. Unfortunately, these user permissions do not allow us to create a new folder at the production site’s root. Their SFTP account does not allow us to create a custom folder within the root directory. It’s also impossible to clone and run the website clone from within the wp-content/uploads folder because all files are run with restricted user/group 133320:600, which cannot execute any PHP files.
On crazydomains servers, the cloning and pushing process results in error 400 on the file copy processing. This indicates that some I/O limits are exceeded.
Until now, we have not found any solution with crazydomains to fix that, and we hope they will try to make ours and other cloning and backup plugins compatible.
Using Amazon Lightsail instance allows only one WordPress site (either a single site or one network site) per instance, and the wp-content folder is located outside of the core WordPress directories path with a symlink to the core path. That’s why WP STAGING can’t clone/push such sites.
As mentioned on their website, they only allow one site per subscription, and they disallow having multiple WordPress sites on the same subscription, so you won’t be able to create a staging site from a website hosted on Elementor Cloud.
The Elementor cloud has limitations, and you will get more freedom by using a fully independent hosting provider.
If you ever want to host your website on a proper independent hosting provider, please don’t hesitate to let us know, and we’ll help you with it.
You can create a blank WordPress site on another server and then use WP STAGING and its award-winning backup feature to migrate the data to that other site. The WP STAGING Backup and Migration feature works 100% even on WordPress.com-hosted WordPress websites.
Due to technical limitations, it is not possible to create a staging site with WP STAGING on the same system in a subfolder. The wordpress.com hosting platform allows only one WordPress site (either a single site or one network site) per instance, where the wp-content folder is located outside the core WordPress directories path with a symlink to the core path. WP STAGING can’t create a staging site or push it to the live site on the wordpress.com platform.
Are You a Hosting Provider and Like to be Listed Here?
Please contact us if you are a hosting provider, company owner, or responsible person for technical questions and if you want to ensure that WP Staging works with your hosted sites.
If you use a hosting provider not on this list but can confirm it works, just let us know, and we’ll add it here.