Wordfence blocking traffic to an add-on domain


We host multiple sites on VPS server running cpanel. The primary site (in public_html) is a WordPress site running WordFence. An add-on domain in a nested folder (plublic_html/addon/) is a WordPress site that doesn’t currently have WordFence installed. Yesterday, we upgraded the addon site to the current version of wordpress (from version 4.9.24) and after that some code stopped working. The site uses Divi, and the code inside of “Code” modules started rendering as text. When we tried resaving them, it would give an error. Eventually, I traced the error to a 403 error due to being blocked by WordFence. In order to get around this, I had to go into the firewall settings on the main site and add an exception.

Is this expected behavior? Should a WordFence install on one domain be impacting a separate domain?


This site will teach you how to build a WordPress website for beginners. We will cover everything from installing WordPress to adding pages, posts, and images to your site. You will learn how to customize your site with themes and plugins, as well as how to market your site online.

Buy WordPress Transfer