You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the beginning, the function was working perfectly but all of the sudden like 3 days ago things just changed. when I query it returns the private IP address of the network load balancer. My config is like
client -> Network LB -> Application LB -> Nginx -> Django server
I just call the function with default values, I didn't pass the arguments like proxy count or trusted IPs. Are these values a must or it is the issue with LB configuration?
Any idea, please help?
The text was updated successfully, but these errors were encountered:
@elkd I do recommend to;
1- pip uninstall django-ipware and pip install django-ipware. If that solves the problem, then great if not cont. w/ step 2
2- If it worked, and it is not working now, if the ipware version is not changed, then look at the network LB for misconfiguration
3- If you don't have access to the upstream network LB config, then you are out of luck ..
ipware can show you what it receives. If the bad ip or spoofed IP is passed down the chain, then you may not be able to do anything about it.
Thank you so much for your prompt response. The issue is with the Network Load Balancer, I'll close the issue for now as I communicate with the infra guys. If the server still misbehaves I'll re-open the issue.
In the beginning, the function was working perfectly but all of the sudden like 3 days ago things just changed. when I query it returns the private IP address of the network load balancer. My config is like
client -> Network LB -> Application LB -> Nginx -> Django server
I just call the function with default values, I didn't pass the arguments like proxy count or trusted IPs. Are these values a must or it is the issue with LB configuration?
Any idea, please help?
The text was updated successfully, but these errors were encountered: