[FIXED BUG] mod_rewrite stopped working. All pages on WordPress sites show 404

Follow

Comments

14 comments

  • Avatar
    Juanjo Sánchez

    ¡IT DOESN'T WORK!

    Después de actualizar WordPress Toolkit a 4.8.1 ejecuto plesk repair web y en todas las webs del servidor dejan de funcionar los redireccionamientos, esto es un problema muy muy grave.

     

     

    0
    Comment actions Permalink
  • Avatar
    Haumanto

    Re-apply these security measures will break.

    • enable bot protection
    • block author scan

    I had to leave those 2 unsecured for the site to work.

    Furthermore, I think subdomain within the same subscription which doesn't have WP but still use .htaccess rewrite rule also breaks because of this bug and don't know how to fix that particular subdomain because it isn't WP site, thus no WPToolKit.

    0
    Comment actions Permalink
  • Avatar
    porta nicolas

    I have 404 errors on all the pages of several sites located in a sub-domain.

    I tested the "workaround" solution but in my case it does not solve the problem.

     

    I am on WPTOOLKIT version 4.8.1-3636 and 18.0.26 PLESK.

    1
    Comment actions Permalink
  • Avatar
    Denit Support

    A faster way to do it 1 site at a time is the following:

    So let's do the following it then, let's revert all changes done on the instances.

    1. Extensions > Wordpress Toolkit > Installation Tab > Security > Select All instances > Revert > Enable hotlink protection, Block authors scan and Enable bot protection

    2. Run plesk repair web -y on CLI

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hi all,

    Please execute also web server reconfiguration:

    Tools & Settings > Diagnose & Repair > Web & FTP Servers > Repair

    Or the same from SSH:

    plesk repair web -y

     
    0
    Comment actions Permalink
  • Avatar
    porta nicolas

    I just performed the procedure on ALL sites, then I execute  "plesk repair web -y" command via SSH and it works now.

     

    Thanks Anton

    2
    Comment actions Permalink
  • Avatar
    Ion Vrinceanu

    This solution is only for vhosts that have WP Toolkit. What about vhosts that have installed WordPress without WP Toolkit?

    1
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hi Ion, Wordpress domains without WP Toolkit can be affected in case there is another domain under the same subscription which has WP Toolkit instance installed. The same steps to disable security measures and do reconfiguration should also solve instances not from WP Toolkit as well.

    0
    Comment actions Permalink
  • Avatar
    Ion Vrinceanu

    Ahh, there was a subdomain I've missed. Thanks, this fixed the issue.

    0
    Comment actions Permalink
  • Avatar
    Victor Amil

    This issue is happening also in Plesk Onyx.

    After a upgrade from Plesk Onyx to Obsidian its needed to follow this instructions and upgrade the WordPress Toolkit.

    Thanks for the fix.

    0
    Comment actions Permalink
  • Avatar
    Tony (Edited )

    wow, it's been a nightmare trying to troubleshoot this across two servers overnight.  trying this fix now! the only workaround i had found was switching php from FPM served by Apache to FPM served by Nginx. 

    Yay- it worked to fix the first domain I tried it on, Denit Support, thanks!

    0
    Comment actions Permalink
  • Avatar
    Rob Marlbrough

    This was driving me nuts, only affecting one site out of many, and I use WordPress toolkit on them all, but perhaps bot protection or block authors was not enabled, not sure. 

    The updated toolkit resolved the issue for me!

    0
    Comment actions Permalink
  • Avatar
    Nickea

    I am still having issues. I did everything mentioned above and nothing. Took me a while to find this as well. Any other suggestions? 

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Nickea

    As I can see, you've contacted support and the issue was resolved. 

    The cause was web server misconfiguration.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request