Your access to this service has been limited. (HTTP response code 403)”

Hello @blacksix and thanks for reaching out to us!

If you’re using a page builder of some sort to post, the WAF might have thought it was a malicious request by mistake (false positive). An easy way to resolve this is to set the WAF into Learning Mode.

From the Wordfence Dashboard click on Manage WAF. Then you will see Basic Firewall Options > Web Application Firewall Status. Change the option to Learning Mode. Now perform the actions that were causing issues. This will help Wordfence learn that these actions are normal and it will allow them in the future. After you have finished performing the actions, switch the WAF from Learning Mode back to Enabled and Protecting. Now test to see if these actions work correctly.

https://www.wordfence.com/help/firewall/learning-mode/ is an amazing resource for learning more about the WAF and learning mode.

Thanks again!

Hello @wfadam
Thank you very much.
Your kind response impressed me.

However, this problem has not been solved.

I changed to learning mode, tried it, but this did not solve the problem.

I definitely want to solve this problem. Is there any other way?

Thanks for letting me know!

Another way to try and resolve this is to head over to your Wordfence > Tools > Live Traffic page and find the actual block that is occurring. The best way to do this would be to attempt the action that is being blocked, then head over to the Live Traffic page. You should see the block here, then click on it to expand it. It might be detecting it as an XSS attack. You can click “Add Param to Allowlist” and that should correct the issue.

Let me know what you find!

Thanks again!

Hello @wfadam
I’m really grateful for your answer.

I tried the way you told me.
Can you see the screenshot?

View post on imgur.com

Do you see [Type: Blocked]?
right! Wordfence blocked it.

And as you told me, I clicked “Add Param to Allowlist”.
But it still doesn’t work properly.

I found a problem, why isn’t it solved?
Do you have another problem?

It’s possible that each of these requests has a different Param then.

Which page builder is it that you’re using?

Can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

Thanks again!

Thank you for your help to me.
I have sent an email and I am waiting for their reply.

See you @wfadam ^^

I was not able to locate the diagnostic.

Could you do the “Export” option on the diagnostic page and then attach it to an email to wftest @ wordfence . com with subject ” blacksix for WFADAm “.

Thanks!

@wfadam Hello.

I just sent you an email.
Check it please.

Thanks for sending that! I did receive it this time!

The diagnostic looks to be good. Everything is in the right place.

Can you try disabling Wordfence, and see if you’re still getting the 403 error for me?

Thanks again!

Hello @wfadam

I disabled the plugin and tried again.
But the error is the same.

I am using a bulletin board plugin.
There are two ways to upload image files here.
1) Through the writing editor (upload image file)
2) A method of uploading by copying and pasting the html code of the image file uploaded to imgur. com.

1) Image file is uploaded normally.
But the 2) method is not.

Until the 403 error occurred, the image file was uploaded normally in the 2) method. But not now.

Why the hell is there an error?
It’s too stuffy…
Is there another workaround?

If its still happening with Wordfence disabled, then something else is causing the block.

A 403 is typically a Firewall that is causing the block. I would reach out to your host or if you have a CDN, you could reach out to them with this issue. They should be able to look into the logs to see what is happening.

Let me know what you find!

Thanks again!

Okay. @wfadam

I’ll keep looking for other problems with it.

If I know the exact cause, I’ll let you know.

Thank you so much. See you again ^^