Relevanssi Forbidden

Resolved Jarada
(@jarada)

9 years, 1 month ago
```
403 Forbidden

A potentially unsafe operation has been detected in your request to this site, and has been blocked by Wordfence.

If you are an administrator and you are certain this is a false positive, you can automatically whitelist this request and repeat the same action.

  I am certain this is a false positive.

Whitelist This Action
```
This happens whenever we try to save options or index the site with Relevanssi while Wordfence Firewall is active.

We’ve tried confirming it as a false positive and putting the firewall into and back out of learning mode (which let the operation succeed with the firewall disabled), but neither option has allowed us to solve the issue.

While disabling the firewall to update Relevanssi is a current workaround, we’d prefer a longer term fix. Any ideas?
- This topic was modified 9 years, 1 month ago by Jarada.

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

Plugin Support wfphil
(@wfphil)

9 years, 1 month ago

Hello,

Sorry to hear that you are having this problem.

I have tried to recreate your issue with the free version of Relevanssi but haven’t been able to.

When I click the “select options” or “Build the index” buttons I also get the same Wordfence 403 Forbidden message on both occassions. However, the whitelist action is successful for me and then either “select options” or “Build the index” appear to be working normally and not being blocked by the firewall.

Can I ask please do you have the latest versions of Wordfence and Relevanssi installed? Also, are you using the free or premium version of Relevanssi?

I will consult my colleagues to see if they can shed some light on your situation.

Plugin Support wfphil
(@wfphil)

9 years, 1 month ago

Hello,

With regards to my reply can I ask if you are seeing any rules added at the bottom of “Firewall” page in the “Whitelisted URL’s” section.

If you do see rules show up there can you set the firewall to “Enabled & Protecting” and then see what happens when you are forced to whitelist again? Are even more rules added?

Thank you.
Thread Starter Jarada
(@jarada)

9 years, 1 month ago
Hey there,

Thank you for your replies.

We are using the latest versions of Wordfence (Version 6.3.6) and Relevanssi (Version 3.5.8), both free.

I’ve just tried the following:
– Tested Relevanssi Save options; 403 error
– Put WordFence into Learning mode
– Tested Relevanssi Save options; all OK
– Checked WordFence firewall rules; no new rules added
– Put WordFence into Enabled and Protected mode
– Tested Relevanssi Save options; 403 error
– Checked WordFence firewall rules; no new rules added

Among the rules that we do have, I have got this one also which I added as a custom rule and has not had any effect:
/wp-admin/options-general.php request.queryString[page] 10/04/2017, 14:15:42 Whitelisted via Firewall Options page
- This reply was modified 9 years, 1 month ago by Jarada.
- This reply was modified 9 years, 1 month ago by Jarada.
Plugin Support wfphil
(@wfphil)

9 years, 1 month ago

Hello,

Apologies for the delay in replying.

I have asked a colleague and they think that they have only seen this happen once before.

On the “Diagnostics” tab on the “Tools” page if you scroll to the bottom of the page and click on the “Send Report by Email” button. Please send it to phil [@] wordfence [dot] com and include your user forum name please.

Thank you.

Thread Starter Jarada
(@jarada)

9 years ago

Hi there,

Apologies for the delay on this myself. I’ve just got this sent to you today.

Plugin Support wfphil
(@wfphil)

9 years ago

Hello,

Thank you for sending the diagnostics report. I will take a look at it for you tomorrow.

Plugin Support wfphil
(@wfphil)

9 years ago

Hello,

Please try adding these Whitelisted URLs and let me know if they work:

URL: /wp-admin/options-general.php
Param: POST Body
Param Name: stopwords

URL: /wp-admin/options-general.php
Param: POST Body
Param Name: index

Thread Starter Jarada
(@jarada)

9 years ago

Hi there,

Fantastic! Put these whitelisted URLs in, went to Relevanssi and saved without any 403 error while the Firewall was Enabled and Protecting.

That worked great! Thank you for all your help with this, it is much appreciated.

Plugin Support wfphil
(@wfphil)

9 years ago

Hello,

Fantastic! I’m glad that worked for you.

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

The topic ‘Relevanssi Forbidden’ is closed to new replies.