646 jili 777 withdrawal philippines.Enjoy Free 888+200 Daily Legal Bonus

Country Detection is not working

Manish S — Wed, 30 Oct 2024 04:38:19 +0000

Please fix “Enable Auto Dial Code Select”, it’s not working as it’s been blocked due to CORS. And since it is using javascript, so it can also be blocked by tracking blockers or Brave browser. Please try adding feature to country detect using backend server.

Screenshot of error – https://share.nmblc.cloud/f029c714

IP Detection turned off for some sites after update

caordawebsol — Wed, 24 Apr 2024 18:10:47 +0000

We have hundreds of sites with Solid Security Basic. Recently after updating from 9.3.1 to 9.3.2, many of those sites suddenly show the banner:

“Important: Some Solid Security features are disabled because IP Detection has not been configured.?Configure Now”

I have to manually go in and select ‘Security Check Scan’ under ‘IP Detection’ or else go back into Features and recheck ‘Security Check Pro’. A lot of times, I find that ‘File Change’ has also been selected when previously it was toggled off.

With many hundreds of sites, this is getting pretty tedious each time when I am performing updates. Will this be fixed?

Incorrect block of IP addresses

Vardan Kocharyan — Wed, 17 May 2023 07:49:03 +0000

A user from IP address 35.208.6.2 tried to login illegally multiple times and WordFence has blocked it. After it nobody was able to login to the site. It was the only IP blocked. After we unblocked all IP addresses and logged in I noticed that the same user tried to login again. When I tried to block it I received the error message “You can’t block your own IP address.”. My IP address is completely different. It seems there is a mistake in IP address comparison algorithm. Could you please check?

Not detecting IP ?

eminozlem — Sun, 14 Mar 2021 22:01:09 +0000

I have someone spamming search queries, but cant detect their IP. I have tried all options under “How does Wordfence get IPs” but its still showing my own server IP.

View post on imgur.com

PS: I am 99.9999% sure it is someone from outside doing this, I’ve blocked them before when I could see their IPs but for some reason I cant see their IPs now, showing server IP instead

Theme for detected IP

bamasstools — Sun, 17 May 2020 08:29:22 +0000

I have one idea , and looking for solution which help me to implement it. Can I show different theme for login screen for different locations? I mean for example detect IP of the visitor and show defined theme for this location or default theme in the case if for the visitor location wasn’t defined any special / custom theme.

Unable to accurately detect IPs Type: IP Detection

sagency — Sat, 07 Mar 2020 19:15:57 +0000

Read other posts on this.

Global Options > “How does Wordfence get IPs?” all options show my matching correct public IP.

Tools>Diagnotics shows my IP with a checkmark.

Why am I still getting this error?

Only recent change made was site was put on new Google platform at Siteground and we had to update domain settings at GoDaddy, but I don’t see how that would be related.

Thanks.

Inaccurate IP detection accompanied by brute-force attack

starsknight — Sat, 07 Mar 2020 00:11:46 +0000

Hi there,

Over the past few days, I’ve gotten an increasing number of “User locked out from signing in” messages, all with the same IP address. But when I went to block it, I realized that WordFence identified it as my IP address. It’s not my IP address. I tried accessing from another IP address, and again, WordFence recorded it as the same incorrect IP address. (In case it is helpful, the IP address WordFence is consistently identifying is 173.236.11.190.)

I tried changing the IP detection method, but no option yields any other result. Every time, it identifies my IP address as the 173 one.

WordFence says it blocked over 25,000 brute-force attacks today, all from this same IP. I don’t know whether this was a real attack, or whether it’s a glitch in the plugin. Stopped seeing new login attempts after I changed the IP detection method a couple times, but it’s now right back where it started (REMOTE_ADDR). Don’t know if the cessation of activity was related, or a coincidence.

Final (possibly relevant) bit of information: While WordFence was misidentifying my IP as of yesterday, it wasn’t until today that I got an error message from it that was unable to accurately detect IPs. After I switched IP detection methods around, the alert disappeared . . . despite the fact that the detection method is right back where it started.

I’ve perused the forums and help pages, but haven’t been able to find anything that’s helped in this particular situation. I’d appreciate any advice you can offer.

Thanks in advance for your time and help!

Help with Canada Detection Code

adminpoumie — Thu, 26 Dec 2019 20:49:04 +0000

Hi – we have GEO IP detection hooked to say no tax in states outside of Illinois and it works beautifully, however, I want to add some code to detect Canada and say our flat rate shipping. I am using a VPN to test and when I goto Canada I am not seeing the text I want, which is this code: [geoip_detect2_show_if country=”CA”]Flat Rate $15 Canada Shipping[/geoip_detect2_show_if]

Here is our current code that is working – and my new code that doesn’t show:
https://prntscr.com/qg4sc7

This is to show that the one code is working:
https://prntscr.com/qg4spj

here is our data source selection:
https://prntscr.com/qg4tbr

Any help as to why the Canada code isn’t working would be most helpful – thank you

Determining IP address

Octave Doctor — Wed, 18 Sep 2019 15:16:06 +0000

This morning I was blocked from my site (the frontend as well as the admin panel) when I went to investigate why it was down (I had received a notification from Jetpack plugin that my site was offline). Actually, the page that came up said that my access to the site had been limited. I tired using the unblock email, which did allow me to the login page. But after entering my credentials it just took me right back to the block page. I was forced to disable Wordfence via SFTP. The reason for the block or limiting was “Blcoked by login security setting”.

I followed the advice in Wordfence documentation to enable the Wordfence Assistant and then disable the firewall and reactivate Wordfence. Once I had Wordfence reactivated I took a look at my live traffic logs, and I believe I’ve found the cause of the trouble but I’m not sure the best way to resolve it. I currently use the free version of Cloudflare CDN, and all traffic to my site is being routed through Cloudflare including my own. When I run “whois” on the live traffic hits, they all return “Cloudflare” as the NetName and OrgName.

The problem with this is that, for some time now, I have been experiencing a large number of brute force attacks using invalid usernames. I have Wordfence set up to block all such attempts as at the moment there are no other users. Because all IP address are appearing to come from the same place (Cloudflare), my own as well as the hacker’s, I was blocked from my site. I could even see on the live traffic list where a hacker was routed on the same exact IP address as me.

Currently Wordfence is set to the default “Let Wordfence use the most secure method to get visitor IP addresses. Prevents spoofing and works with most sites.” Which obviously is not the right setup for my site. I think that using “X-Forwarded-For HTTP header” or “X-Real-IP HTTP header” would be better, but I don’t know which one I should use or if it even makes a difference. In addition to the Cloudflare free CDN, my hosting provider uses Varnish reverse proxy cache, if that makes a difference here.

Geo location of our global dealers

intecprinters — Fri, 28 Jun 2019 15:46:19 +0000

What plugin(s) should we use to replicate this type of feature please?
https://www.secabo.com/en/secabo-c60-v-vinyl-cutter-100-106-065-10/#

If you click the red ‘BUY’ button on that page, a pop-up displays with the choice of outlets in the location near wherever you are located globally.
We want visitors to our website to be presented with the reseller/distributor for our products near to them.

Thanks, Shaun.