The bad .htaccess file written by Bluehost stopped JetPack backup creation.

The bad.htaccess` file written by Bluehost was blocking <strong>Jetpack</strong> backup creation.
Server was overwriting .htaccess file.
They have added a rule as I have pasted below here:

<FilesMatch '^(index.php|auto_seo.php|wp-blog-header.php|wp-config-sample.php|wp-links-opml.php|wp-login.php|wp-settings.php|wp-trackback.php|wp-activate.php|wp-comments-post.php|wp-cron.php|wp-load.php|wp-mail.php|wp-signup.php|xmlrpc.php|edit-form-advanced.php|link-parse-opml.php|ms-sites.php|options-writing.php|themes.php|admin-ajax.php|edit-form-comment.php|link.php|ms-themes.php|plugin-editor.php|admin-footer.php|edit-link-form.php|load-scripts.php|ms-upgrade-network.php|admin-functions.php|edit.php|load-styles.php|ms-users.php|plugins.php|admin-header.php|edit-tag-form.php|media-new.php|my-sites.php|post-new.php|admin.php|edit-tags.php|media.php|nav-menus.php|post.php|admin-post.php|export.php|media-upload.php|network.php|press-this.php|upload.php|async-upload.php|menu-header.php|options-discussion.php|privacy.php|user-edit.php|menu.php|options-general.php|profile.php|user-new.php|moderation.php|options-head.php|revision.php|users.php|custom-background.php|ms-admin.php|options-media.php|setup-config.php|widgets.php|custom-header.php|ms-delete-site.php|options-permalink.php|term.php|customize.php|link-add.php|ms-edit.php|options.php|edit-comments.php|link-manager.php|ms-options.php|options-reading.php|system_log.php)$'>
Order allow,deny
Allow from all
</FilesMatch>

<strong>Too many other files</strong> required by WordPress to function properly are not included in the list above.
For example:
load-jetpack.php|class.jetpack.php|site-health.php|tools.php|theme-install.php|plugin-install.php|update-core.php

The server was blocking JetPack Backup this way too.
Finally, I had to add a rule right after their rule as below:

<FilesMatch ".*\.php$">
Order allow,deny
Allow from all
</FilesMatch>

Jetpack Backup created successfully now.
We can access full WordPress functionality now.
I communicated with the Bluehost support team too. But the solution they provide could not retain after a few minutes because the server changed the .htaccess file to add its own rule again.
I am writing this topic here because I assume that you (Jetpack Team) are better to dialog with Bluehost. `

• This topic was modified 3 years, 7 months ago by gyjafar.