WP Staging Pro is tested well and works on most of the available hosting providers and servers. If your hosting provider has not mentioned here this only means that we have not tested the plugin for the respective provider. Chances are good that it still works on your hosting system.
Compatible Hosting Providers
- Amazon AWS
- Microsoft Azure
- InMotion Hosting
Incompatible Hosting Providers
WP Staging does not work with the following hosting providers due to server restrictions and/or due to less powerful systems.
There are only a few known hosting provider so far which are not compatible with WP Staging and which leads to a bad experience.
IONOS 1&1 Web Hosting
There are IONOS plans which run WordPress in a closed environment with the user/group 43:600. This does seem to be a preconfigured WordPress installation, probably made by a one-click installation script. These user permissions do not allow us to create a new folder in the root of the production site. Even their sFTP account does not allow us to create a custom folder within the root directory. It’s also not possible to simply clone and run the website clone from within the wp-content/uploads folder because of all files in there run with restricted user/group 133320:600 which is not allowed to execute any PHP files.
On crazydomains servers, the cloning and pushing process results in errors 400 on the file copy processing. This indicates that some I/O limits are hitten.
Until now we have not found any solution with crazydomains to fix that and hope they will try to make ours and other cloning and backup plugins compatible
Bitnami WordPress AWS
Activated post-name permalinks are not supported on WordPress Bitnami instances due to the reason that Bitnami does not use .htaccess in the root folder of the website. It ignores any .htaccess file there.
Bitnami does not use .htaccess files, instead all the htaccess configurations are added to a file called: /opt/bitnami/apps/APPNAME/conf/htaccess.conf.
So if you want to make permalinks working you will need to modify the htaccess.conf
So whenever you create a clone of your website it uses the .htaccess outside the root. As a result, permalinks might not be working as expected.
Another option is to keep the permalinks on the plain settings, then you will not need to change the htaccess.conf at all.
Please get in contact with us if you are hosting provider company owner or responsible person for technical questions and you like to ensure that WP Staging works with your hosted sites.
If you are using another hosting provider and you can confirm that WP Staging runs on it please send us the name of it.
We are going to add it to that list.