dciphered

Hi Gerroald,

Appreciate the detail within your reply however it deviates off point to my question.

I’m well aware the anatomy of cyber attacks and the kill chain process, especially in context of WordPress, and “security through obscurity” is a complimentary principle with absolute value when it comes to a good protection strategy, albeit, on it’s own is not enough.

Most seasoned security folk will manage risk through a multilayered approach (a solid defence in depth strategy) and obfuscation makes part of that. There are many ways to throw attackers off course (if you know what you’re doing) when it comes to hiding your WP deployment however when you have a WAF solution with neon lights that tells the attacker they’ve been blocked by a Worpdress plugin, then it defeats the purpose of what I’ve mentioned above.

So back to my point, having a custom error page helps alleviate this issue and it “absolutely” helps with security which is no doubt why you’ve had this topic asked before. It’s a simple question with a simple answer – can it be done without modifying Wordfence code/php files? Most network and application layer security solutions provide the ability to customise error pages, that’s what we need here.

I hope this adds further clarity to my request.

Any updates on this??

Hi Slava,

Yes correct, all was working prior to the recent updates. Just an FYI, I’ve actually installed a different SMTP plugin to validate my assumptions and I can validate that everything works as it should. Reverting to WP SMTP Mail causes the issue again.

1. I’m using Amazon SES as the configured mailer.
2. Yes it does, test emails work fine.
3. Yes i downgraded and things appeared to work ok however I did notice that some emails were arriving intermittently, not consistently.
4. Meaning, that we have a few WP servers with sites, including our Prod and Dev boxes and all of them were experiencing the same issue. Also, Yes, Opcache is enabled however as I mentioned before, the other SMTP plugins we’ve tested work without hiccup.

Something’s definitely gone wrong since 1.5x.

Hi Alex,

As originally assumed, it was a wild coincidence caused by another process.

Appreciate your willingness to assist and the quick turnaround.

OK, not exactly sure what happened here but the issue has been resolved since WP 5.1 was deployed. Assuming that it was a WP issue and not a plugin related problem.

Problem fixed.

One additional note to add. When first enabling CMP (with WP Rocket also enabled), everything works fine. However, when I access the site using the CMP secret URL, bypassing the coming soon page, WP Rocket obviously caches the home page which I would assume is why after a while, others can also see the home page (and any other page visited) even if CMP is enabled.

All plugins disabled and still the same problem…