Thanks Nayeem. I did some further inspection, and I realized the issue actually started when I switched to Azure App Service last week.
I tried adjusting the IP detection in wp-config.php like this:
if ( isset($_SERVER[‘HTTP_CF_CONNECTING_IP’]) ) {
$_SERVER[‘REMOTE_ADDR’] = $_SERVER[‘HTTP_CF_CONNECTING_IP’];
$_SERVER[‘HTTP_X_FORWARDED_FOR’] = $_SERVER[‘HTTP_CF_CONNECTING_IP’];
$_SERVER[‘HTTP_CLIENT_IP’] = $_SERVER[‘HTTP_CF_CONNECTING_IP’];
}
Unfortunately, this didn’t fix it — in the download history, all users are still shown as coming from 169.254.129.1. It looks like WPDM might not be using $_SERVER[‘REMOTE_ADDR’] consistently, or perhaps Azure is overriding it in a way I can’t fully control.
Could you please advise:
Which header does WP Download Manager use to detect client IP?
Is there a way to force WPDM to use HTTP_CF_CONNECTING_IP (or another header) when it is available?
If not, is there a recommended workaround for Azure App Service environments?
Thank you so much for your help
