Hi @vegaspro22,
Your developer mentioned a few issues, but I believe there are two settings you can change to allow Wordfence to work.
1. Enabling MySQLi storage engine
By default, Wordfence will save firewall related data within /wp-content/wflogs/*. However, in an instanced setup, the file-system is read-only.
To get around this, add the line define('WFWAF_STORAGE_ENGINE', 'mysqli'); after <?php on a new line within /wordfence-waf.php.
Wordfence will then save all its firewall data within the database instead of attempting to use the file-system.
https://www.wordfence.com/help/firewall/mysqli-storage-engine/
2. Making sure that inbound IP addresses are correct
If your site is also behind a proxy or load balancer, you may need to change How does Wordfence get IPs.
To do this, find out what your IP address by visiting https://www.google.com/search?q=what+is+my+ip and then compare that to Your IP with this setting to make sure that they match.
3. Using Import/Export settings when migrating
If you’re moving your WordPress site to another host, you should go into Wordfence -> Tools -> Import/Export options and copy the exported token.
Once your new site is up, reinstall Wordfence (remembering to check off Delete tables and data on deactivation) and import the token.
—
What I would recommend is setting up a staging site to see if Wordfence works properly with your environment first. If you do find any issues, feel free to come back and we’ll see if we can tweak some other settings to get it to work.
Dave