Sucuri Website Firewall – Cloudproxy – Access Denied

734
Sucuri Website Firewall - Cloudproxy - Access Denied

Here we can see “Sucuri Website Firewall – Cloudproxy – Access Denied”

Why does Access Denied — Sucuri Website Firewall’ error happen?

Sucuri Firewall is among the Best Internet Application Firewall. What’s more, it functions nicely in safeguarding WordPress sites in the machine.

In addition, it shields the site from outside attacks keeping it secure.

But, in the event, the website blocks the Sucuri IP addresses. Subsequently, access denied errors appear on the site.

How we Repair Sucuri error readily?

We’ve got over a decade of experience in handling servers. As a result, we view many customers confronting issues with Sucuri.

Today, let us see our Service Engineers fix this error.

Also See:  How to: Fix Norton Antivirus Fails to Update on Windows 10

Lately, one of our customers approached us with an error access Denied — Sucuri Website Firewall‘. Unfortunately, he obtained this error when obtaining his site.

On checking, we discovered that the user needed a Sucuri firewall put on his WordPress. And that was obstructing its IP address. Thus it had been showing access denied error on the site.

We allowed that the Sucuri IP addresses by simply adding them into the .htaccess file.

This is the code that we used from the .htaccess file.

Order deny, allow

<FilesMatch ".*">
Order deny,allow
Deny from all
Allow from 192.88.134.0/23
Allow from 185.93.228.0/22
Allow from 66.248.200.0/22
Allow from 208.109.0.0/22
Allow from 2a02:fe80::/29
</FilesMatch>

Whitelisting with IPtables

Additionally, we also allow the IP addresses from the server in line with the firewall utilized. So, for example, if we’re using IPTables, we’ll allow the IP addresses of Sucuri from the IPTables firewall.

Also See:  How to Download Outlook Assistant

By way of instance, we helped to allowlist the assortment of IP addresses in IPTables as follows.

Originally we logged in to the server through SSH.

Subsequently, we let incoming links out of 192.88.134.0/23

iptables -A INPUT -i eth1 -s 192.88.134.0/23 -j ACCEPT

Subsequently allowed incoming links to 192.88.134.0/23

iptables -A OUTPUT -i eth1 -d 192.88.134.0/23 -j ACCEPT

Therefore we allowed that the selection of IP addresses. At length, the Sucuri mistake was solved.