IP address being blocked, that isn't on the blocked list

One of my users is unable to log in. He’s getting the error “You can’t log in as username from that IP address” (where username is his actual username). I’ve whitelisted 148.64.0.0/21, which should match his public IP. It’s 148.64.2.45, according to google. Here’s my Screened IPs config:

image

Any ideas why this person is being blocked? What else can I do to troubleshoot this?

Looks correct to me… are IP addresses not correctly sent to the app via unusual proxy/routing config? What happens when you test this by adding a test IP to the block list, then logging in from that IP?

1 Like

It turns out that due to using AWS CloudFront, discourse sees all users as having an IP address belonging to AWS CF.

2 Likes