Replies: 1
What is the default setting for “whitelisted services” setting. It’s not in the documentation. My clients are in USA.
Extra credit – If the following are enabled by default, why? What is important to understand about these three.
Uptime Robot
StatusCake
Seznam Search Engine
Thanks
Replies: 1
I hope you find this question interesting and sort of fun.
On the last couple of days of the month, a client site keeps hitting the limit for the “number of views” allowed for their privacy policy banner. If they could reduce the number of views per month by just a bit, the nag to up the subscription would go away.
This client work is hyper-local. They have Wordfence free installed. My idea is that a lot of views are not real traffic. If we blocked some traffic from around the world via country blocking, they would solve the view limit problem plus get the advantages of Wordfence Pro.
This of course depend on how-it-works. Does this logic sound correct?
Thanks
Replies: 2
I have added “Admin” to the “Immediately block the IP of users who try to sign in as these usernames” list. However, “Admin” attempts to log in to my site regularly – multiple times a day, often in bursts. I’m assuming I’m doing something wrong, but I can’t figure it out. Any advice most appreciated. TIA.
WordFence Free Version 7.4.11
WordPress Version 5.5.1
Replies: 0
Dear Wordfence team,
I am running WordPress on a Google App engine which means the filesystem is read-only. I saw this article of yours: https://wordpress.org/support/topic/wordfence-waf-wont-run-on-a-read-only-system and I wanted to know if support for read-only filesystems will still work in the described way? Since the article is two years old.
And if it does, what is the mentioned functionality that I would not have?
Best regards,
Wolfram
Replies: 0
I installed a theme and child for a new business directory site and see that Wordfence has flagged over 1700 theme files as red alerts. Just how serious is this? The company providing the theme says there are no security issues, but I’ve been a fan of Wordfence too long to believe that. This theme shows my actual user name, not nickname, in the page code of every listing. That alone seems to challenge their security basics from my POV.
Here are some of the alerts…
BTW, great job on FastOrSlow.com. Lovin’ it.
Unknown file in WordPress core: wp-includes/wp-diff.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Need help with a hacked website?
Our team of security experts will clean the infection and remove malicious content. Once your site is restored we will provide a detailed report of our findings. Includes a 1-year Wordfence Premium license.
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Util.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/X25519.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/XChaCha20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/XSalsa20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Crypto.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Crypto32.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/File.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/PHP52/SplFixedArray.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/SodiumException.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/spl-autoload-compat.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/taxonomy.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/template-loader.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/template.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/theme-compat/comments.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/theme-compat/embed-404.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/theme-compat/embed-content.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/theme-compat/embed.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/theme-compat/footer-embed.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/theme-compat/footer.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/theme-compat/header-embed.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/theme-compat/header.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/theme-compat/sidebar.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/theme.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/update.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/user.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/vars.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/version.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-nav-menu-widget.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-archives.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-calendar.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-categories.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-custom-html.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-links.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-media-audio.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-media-gallery.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-media-image.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-media-video.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-media.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-meta.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-pages.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-recent-comments.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-recent-posts.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-rss.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-search.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-tag-cloud.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets/class-wp-widget-text.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/widgets.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/wlwmanifest.xml.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/wp-db.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Curve25519/Fe.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Curve25519/Ge/Cached.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Curve25519/Ge/P1p1.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Curve25519/Ge/P2.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Curve25519/Ge/P3.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Curve25519/Ge/Precomp.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Curve25519/H.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Curve25519/README.md.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Curve25519.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Ed25519.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/HChaCha20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/HSalsa20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Poly1305/State.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Poly1305.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Salsa20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/SecretStream/State.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/SipHash.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/Util.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/X25519.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/XChaCha20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core/XSalsa20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/BLAKE2b.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/ChaCha20/Ctx.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/ChaCha20/IetfCtx.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/ChaCha20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Curve25519/Fe.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Curve25519/Ge/Cached.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Curve25519/Ge/P1p1.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Curve25519/Ge/P2.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Curve25519/Ge/P3.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Curve25519/Ge/Precomp.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Curve25519/H.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Curve25519/README.md.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Curve25519.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Ed25519.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/HChaCha20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/HSalsa20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Int32.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Int64.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Poly1305/State.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Poly1305.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/Salsa20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/SecretStream/State.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/src/Core32/SipHash.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/namespaced/Core/Poly1305.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/namespaced/Core/Salsa20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/namespaced/Core/SipHash.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/namespaced/Core/Util.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/namespaced/Core/X25519.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Ignore
Details
Unknown file in WordPress core: wp-includes/sodium_compat/namespaced/Core/XChaCha20.php.1471916354
Type: File
Issue Found September 29, 2020 9:21 pm
High
Replies: 0
Wordfence is blocking the instagram API key – can you tell me how to unblock it in wordfence please.
Thanks
Robin
Replies: 0
As the primary admin for a website I webmaster for, I logged in and edited the profile for our President to move him up to admin privileges. Wordfence has notified me 4 times now that this was done out of wordpress as found during a scan. I have marked it fixed 3 times. How do I stop the scan process from thinking this is a problem.
Replies: 0
I can’t get back into my website and even when trying to send a recovery email I don’t receive anything.
I’ve been using this plugin for a while and never had issues but this is really bad especially since I cant update the site for the client.
Replies: 2
I built and maintain many WP sites using WF and have never had a problem. However for this site (mainesilc.org) WordFence keeps blocking me when I try to login with my admin credentials.
Exact reason: Block Technical Data
Block Reason: You have been temporarily locked out of this system. This means that you will not be able to log in for a while.
Time: Thu, 1 Oct 2020 19:36:31 GMT
I’ve used the UNBLOCK EMAIL to get it (successfully) three times, but I keep getting blocked.
I’ve looked through the documentation and am not seeing a solution other than to disable “advanced blocking” – Is that what I do? All of my other Wp with WF work fine and this has never happened before.
Replies: 0
New clients can register for an account to the page: https://groeidala.be/registreer_voor_downloadarea/
Since some time Wordfence is blocking new clients. All plugins are up to date.
There was an issue with Profile Builder in februari, but this should be fixed in the update, so not clear why profile builder is still blocking new requests.
Many thanks for your response.
Sofie
Replies: 0
Hello,
I am trying to optimise the wordfence firewall, i select manual and copy the path it gives me. i can verify wordfence-waf.php has been created.
I then go into the openlitespeed webadmin panel and apply the following to my vhost PHP override
php_value auto_prepend_file = ‘/usr/local/lsws/websitename/html/wordfence-waf.php’
However after restarting the webserver the site only gives error 500s, with the log file stating PHP Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0
I have double checked the paths and it all seems correct, not sure what i am missing?
Thanks,
Replies: 0
Hello,
We have a site running php 7.2.x, MySQL 5.7.x, WordPress 5.2.x and WordFence 7.4.x. We’re getting the following error:
WordPress database error Table ‘###.wp_wfHits’ doesn’t exist for query
The table exits, but in the database it’s all lower case. Is there any way to correct this issue?
Thanks
Replies: 3
This may/may not be a Wordfence issue.
I’m suddenly getting a 404 when I try to access Installed Plugins page and Wordfence Scan on a 5.5.1 site under development that’s about to be launched. I can access all other pages, including Add New plugins page. Chanced upon the error when I tried to access Wordfence Scan.
No errors on the frontend
Following a suggestion, replaced wp-admin from a fresh download – no joy
Also renamed plugins folder; no change either.
There are no redirections
Nothing in htaccess that can cause this.
Site and plugins are all updated (as of a few days ago)
The only plugins I have are:
akeebabackupwp
akismet
contact-form-7
disable-comments
disable-xml-rpc-pingback
meow-gallery
popup-maker
rara-one-click-demo-import
shared-counts
ultimate-category-excluder
wordfence
wp-google-maps
wp-hummingbird
wps-hide-login
Help appreciated. Thanks in advance.
Replies: 1
I keep seeing this: The last rules update for the Wordfence Web Application Firewall was unsuccessful.
I can’t dismiss it. I can’t manually update it. I have tried all the suggestions offered on another thread (that was marked resolved) and nothing has worked.
Is there something I’m missing? Does anyone know how to fix this?
Replies: 1
Hello after trying to access some parts of my WP Dashboard, I received this message. I’ve already scanned my site and nothing was found and the site has had no changes to any of the File Manager files, plugins or themes. Please help!
Warning: require_once(/home/customer/www/mydiyrealestate.com/public_html/wp-content/plugins/wordfence/vendor/autoload.php): failed to open stream: Too many open files in /home/customer/www/mydiyrealestate.com/public_html/wp-content/plugins/wordfence/waf/wfWAFGeoIP2.php on line 3
Fatal error: require_once(): Failed opening required ‘/home/customer/www/mydiyrealestate.com/public_html/wp-content/plugins/wordfence/waf/../vendor/autoload.php’ (include_path=’.:/usr/local/php73/pear’) in /home/customer/www/mydiyrealestate.com/public_html/wp-content/plugins/wordfence/waf/wfWAFGeoIP2.php on line 3
Replies: 1
Hi there,
I’m really frustrated with this problem. Every time wordfence blocks me without any reason. Even I didn’t try to log in or any other log in try. Earlier, wordfence detect my all log in attempt from singapore and a google ip address. But that’s not my actual ip and location. Also I got some xmlrpc etc from the same ip. I don’t know how wordfence is collecting my ip. I’m not using any vpn or anything.
Here is a Screenshot – https://prnt.sc/urx3q5. Please help me guys 🙁
Best Regards,
Amrit
Replies: 0
Hi,
Is there any way to completely remove my IP from Wordfence statistics? I tried using the “List of comma separated IP addresses to ignore”, but my logins are always registered.
Thanks
Replies: 1
We have a client with heavy disc space usage, and when I poked around today, what I found is a log file called wf-licensing.log located in their wp-content directory. In the case of our customer’s web site, this log seems to be growing by the minute and currently at 691 mb. We need to clear this file — is it safe to delete it? Will it be recreated if we do?
And also, why is it in such heavy use? What is being logged? Can we stop it from growing at an exponential rate?
Thanks for your help!
Replies: 0
Trying to install the Google Analytics tracking code on my second website, and a 403 error from Wordfence keeps coming up (A potentially unsafe operation has been detected in your request to this site).
Plot twist: I don’t even HAVE Wordfence installed on this site, though it is on my other website. So is it recognising me as the same user? And how do I fix the error? The Help section says I should go to “live tracker” and whitelist it there, but I can’t go to live tracker if I don’t even have Wordfence installed!?
Replies: 0
Hello,
I’m using the 2FA login security feature with Wordfence security plugin, but recently I’m facing an issue with the code generated on my Google Authenticator App. in which I have to enter the correct generated code twice in order for my WP login page to accept it.
It seems to be a delay in the code synchronization between my WP Wordfence security plugin & Google Authenticator App. !!
Every time I attempt to login, I enter the code generated on my Google Authenticator App. and WP login page return “Error” wrong code, then I have to enter it again before it get change for the WP login to accept the code and allow login!!
I’m not sure what is the issue here, I’m entering the correct code but why WP login not accepting the code when it is freshly generated but it accept the same code after 30 seconds or more and before the code change (the code chage every 1 Min.)
Pls. help,
Thank you,