After update rankmath Not Working – After Rollback Functionality broken

Hello,

We might need to take a closer look at the settings. Please edit the first post on this ticket and include your WP logins in the designated Sensitive Data section.

It is completely secure and only our support staff has access to that section. If you want, you can use the below plugin to generate a temporary login URL to your website and share that with us instead:

https://wordpress.org/plugins/temporary-login-without-password/

You can use the above plugin in conjunction with the WP Security Audit Log to monitor what changes our staff might make on your website (if any):

https://wordpress.org/plugins/wp-security-audit-log/

We really look forward to helping you.

Hi there,

Thanks for the follow up.

Your site is locked behind a HTTP directory password, please share some credentials to get across this so that I can login and check this issue.

I am looking forward to helping you. Thank you.

Hello,

Please update to version 1.0.29, we have just fixed the compatibility issue.

In regards to the 404 error on the sitemap, could you do the following:

1. Head over to WordPress Dashboard > Settings > Permalinks

Hit the save button once.

2. Go to WordPress Dashboard > Rank Math > Sitemap Settings

Hit the save button once.

That should fix the issue.

If it doesn’t, please do let us know so we can look at this further.

Hi there,

Thanks for the follow up.

Your Nginx server is blocking redirects required to create the sitemap and thus you will need to add some manual redirects. Please check you Nginx config file and add the following code:

# START Nginx Rewrites for Rank Math Sitemaps
rewrite ^/sitemap_index.xml$ /index.php?sitemap=1 last;
rewrite ^/([^/]+?)-sitemap([0-9]+)?.xml$ /index.php?sitemap=$1&sitemap_n=$2 last;
# END Nginx Rewrites for Rank Math Sitemaps

This should then fix the issue. Thank you.

Hi there,

I am glad that this is now working correctly.
Is it possible that your host might have coincidentally made some configuration changes recently that might have caused this?

Please let us know if the issue pops up again so that we can investigate further.
Thank you.