Closed dphiffer closed 7 years ago
I can confirm I've been seeing these too.
Ran sudo ntpdate time.nist.gov
on the server, in case it's a time drift issue.
Continued issues leads me to believe the cause was not time drift.
I tracked this down. The cause was that $GLOBALS['_SERVER']['REMOTE_ADDR']
contained the IP address of the ELB instead of the client IP.
Yeah, you don't want to use that. You should use the remote_addr
function:
Hmm that gives me back 192.168.18.245
on dev. I wonder if we need to tinker with how the headers are set upstream?
It's possible we're passing a different header. I would start with the proxy configs.
Pretty sure this is fixed now.
Seemingly resolves itself after reloading the page, but wtf?