Hi @getzd, thanks for getting in touch.
We generally suggest not hiding the WordPress login pages as this can cause issues on your site where other plugins require this path. With certain “security through obscurity” methods such as this, we feel this only serves to slightly slow down somebody with malicious intent rather than stop them entirely: https://www.wordfence.com/blog/2017/10/should-you-hide-wordpress-login-page/
However, having said this some of our customers do still wish to hide login pages like this and I’ve not seen this plugin cause specific problems with the scan before. Have you already tried starting scans remotely from the Wordfence > Tools > Diagnostics > Debugging Options section? If not, please do so.
If that’s doesn’t work, please do the following steps for me:
- Go to the Wordfence > Tools > Diagnostics page
- In the “Debugging Options” section check the circle “Enable debugging mode”
- Click to “Save Changes”.
- CANCEL any current scan and start a NEW scan
- Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log once the scan finishes and paste them in this post.
Wordfence > Tools > Diagnostic > Debugging Screenshot
This will help me see exactly what is happening when the scan fails.
Let me know if you have any questions!
Peter.
