Source evidence

cannot login – Cloudflare?

Loginizer · support · 2025-07-17T14:38:00+00:00

Loginizer plugin evidence original source source API

questionsentiment

highseverity

0.66relevance

5replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 31 rows with source links

16.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

rainacorn resolved

Hello. When I try to log in, I get a message asking me to wait 15 hours. I’ve done some troubleshooting and can confirm the following: – MY IP in the Loginizer Dashboard and on whatismyipaddress.com are different – I’m using Cloudflare I’ve seen a couple forum posts where the developer asked about Cloudflare but that wasn’t the issue. I couldn’t find any documentation of what to do if using Cloudflare. Thanks! Hello, Would you please try setting HTTP_X_FORWARDED_FOR in the dashboard of the Loginizer Method field, which is just beside where your IP is shown. See if that fixes the issue you are facing. Regards, Vardan I’ve tried all the methods in the drop down and none of them change the IP. Hello, Would you please tell if you have tried HTTP_CF_CONNECTING_IP using the custom option? Regards, Vardan That worked for making the IPs match! I’ve re-enabled brute force protection. Previously, it took a while before it started locking me out again. So I’ll follow up in a few days when I try to log in again. Thank You! Hello, Glad to know it worked, let us know if you face any issue again. Regards, Vardan

Commercial Context

Opportunity

admin and client-governance operations

Admin governance for keeping client admin areas controlled, understandable, and safe to maintain

Buyer: agencies, maintenance teams, and client-site operators

Wedge: audit admin changes, role drift, client handoffs, and unsafe settings exposure

Proof Blocked card complete market

Analysis

codex:gpt-5.5

Summary: Loginizer locked the user out for 15 hours because Cloudflare IP detection was wrong until support suggested the HTTP_CF_CONNECTING_IP setting.

Evidence quote: When I try to log in, I get a message asking me to wait 15 hours.

Affected feature: Cloudflare IP detection

setup compatibility security support

Plugin

API

Loginizer

1.0M active installs · 30.9M downloads · rating 96.0

access admin login loginizer security

Comments

5 shown

Vardan 2025-07-17T14:43:00+00:00

Hello, Would you please try setting HTTP_X_FORWARDED_FOR in the dashboard of the Loginizer Method field, which is just beside where your IP is shown. See if that fixes the issue you are facing. Regards, Vardan

rainacorn 2025-07-17T14:52:00+00:00

I’ve tried all the methods in the drop down and none of them change the IP.

Vardan 2025-07-17T15:11:00+00:00

Hello, Would you please tell if you have tried HTTP_CF_CONNECTING_IP using the custom option? Regards, Vardan

rainacorn 2025-07-17T15:52:00+00:00

That worked for making the IPs match! I’ve re-enabled brute force protection. Previously, it took a while before it started locking me out again. So I’ll follow up in a few days when I try to log in again. Thank You!

Vardan 2025-07-18T07:23:00+00:00

Hello, Glad to know it worked, let us know if you face any issue again. Regards, Vardan