Google Search Console – Error 403

Resolved stfa76
(@stfa76)

7 years, 11 months ago
Hi,

For the last 5/6 weeks, I’m witnessing an increased number of “403” errors in the Google Webmaster console: https://ibb.co/chXRco

The recurring pattern seems to point at a regexp I put in the .htaccess file when I changed the permalink two years ago:
```
# Redirect permalink
RewriteEngine on
RewriteRule ^([0-9]{4})([0-9]{2})([0-9]{2})-(\d+)-([^/]+)/$ /?p=$4 [R=301,L]
```
Basically, I redirect all the previous permalinks to the basic WordPress pageid so that WordPress can redirect to the new permalink. It might seems a bit twisted but since I had a lot of internal links prior to this change, it works just fine for old articles without having to edit all of them (800+ posts).

For example, if you take this “old” article:
https://www.digitalcine.fr/20160531-16473-fargo-saison-2-en-blu-ray-chapitre-2-sur-9/

The regexp will redirect here:
https://www.digitalcine.fr/?p=16473

And WordPress will then redirect to the final permalink:
https://www.digitalcine.fr/4k-bluray-dvd/tests-bluray-dvd/16473-fargo-saison-2-en-blu-ray-chapitre-2-sur-9/

But when looking at the error inside the Google Search Console, the bots seem to try accessing this page:
https://www.digitalcine.fr/(%5Ba-z0-9%5C-/%5D+)/16473-fargo-saison-2-en-blu-ray-chapitre-2-sur-9

Is it possible that one of the “All In One WP Security & Firewall” option (inside the .htaccess file) might be conflicting with the regexp I put in place?

Thanks a lot for your help.

Best regards,
Stephane.

Viewing 7 replies - 1 through 7 (of 7 total)

Plugin Contributor mbrsolution
(@mbrsolution)

7 years, 11 months ago

Hi, it is possible that one or more features might be clashing with your permalink structure. Although looking further into your setup, perhaps there might be a better way of achieving your goal.

You might want to start by disabling the following rules.

Enable 6G Firewall Protection:
and or
Enable legacy 5G Firewall Protection:

Then check Google Webmaster console.

Regards

Plugin Contributor wpsolutions
(@wpsolutions)

7 years, 11 months ago

hi,

Is it possible that one of the “All In One WP Security & Firewall” option (inside the .htaccess file) might be conflicting with the regexp I put in place?

Which AIOWPS firewall rules do you have enabled when the issue occurs?
Let’s say for example you’ve enabled all or some of the firewall rules, then you can perform a few simple tests to identify the conflict by disabling one rule at a time and testing during each step to check if the issue goes away.

This plugin has so many firewall rules which are deliberately split up into separate sections because of the scenario you just described.
Not all sites will work 100% with all of the rules enabled due to the fact every site has a unique setup and different behaviours.

So for your case, if the deny bad query strings is preventing some functionality you should leave it disabled.
General rule of thumb is usually this: if you had to choose just one firewall rule to enable it would be the 6G rules because they provide the best all-round coverage/protection.

Thread Starter stfa76
(@stfa76)

7 years, 11 months ago

Thx a lot for your help @mbrsolution and @wpsolutions.

Since I activated a lot of different options in order to achieve the best possible protection, I guess I just have to go back one step at a time now to try and figure out which one is conflicting with my regexp 🙂

Plugin Contributor mbrsolution
(@mbrsolution)

7 years, 11 months ago

Hi @stfa76, yes that would be the best option for you. Let us know when you find the conflicting feature.

Thank you

Thread Starter stfa76
(@stfa76)

7 years, 10 months ago

Hi,

Just a quick update to let you know that I might have found the option that was conflicting with the regexp I put in place in the .htaccess file.

I deactivated this option three weeks ago and since then, I don’t have 403 errors anymore in the Google Webmaster console: “Firewall > Additionnal firewall rules > Characters string advanced filter”

(I’m not 100% sure of the option name since I’m using the french translated version of “All In One WP Security & Firewall”).

Best regards,
Stephane.
Plugin Contributor mbrsolution
(@mbrsolution)

7 years, 10 months ago
Hi stfa76, that is great news.

The following is part of the More Info link next to this feature.

NOTE: Some strings for this setting might break some functionality.
You are therefore strongly advised to take a backup of your active .htaccess file before applying this feature.

And it looks like this feature cannot be enabled in your site.

If your issue is resolved and you don’t need any more help, can you mark this support thread as resolved.

Thank you
- This reply was modified 7 years, 10 months ago by mbrsolution.
- This reply was modified 7 years, 10 months ago by mbrsolution.
Thread Starter stfa76
(@stfa76)

7 years, 10 months ago

Resolved

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Google Search Console – Error 403’ is closed to new replies.