Hi Cris-aian,

This typically occurs because AWS Load Balancers forward traffic using the X-Forwarded-For header instead of the original client IP, and NGINX may not be configured by default to log or trust those forwarded headers.

Here’s how to fix it:

1. Update your NGINX log format to capture the real client IP from AWS:

   log_format main '$http_x_forwarded_for - $remote_user [$time_local] '
                   '"$request" $status $body_bytes_sent "$http_referer" '
                   '"$http_user_agent"';
   access_log /var/log/nginx/access.log main;
   

2. Tell NGINX to trust the AWS Load Balancer IPs so it treats the forwarded IPs as valid:

   set_real_ip_from 0.0.0.0/0;
   real_ip_header X-Forwarded-For;
   real_ip_recursive on;
   

   (You can narrow the set_real_ip_from range to your AWS subnet for better security.)
3. Restart NGINX after saving the changes.
4. Verify by checking if access logs now show the real visitor IPs instead of the AWS Load Balancer IP or blank entries.

This configuration ensures all traffic routed through AWS ALB is properly logged in NGINX and visible in your Odoo access logs.

Hello Cysbros,

Can you share any guide for implementing AWS load balancer for odoo?

Hi,

Try to Configure HTTP Load Balancer Using the Nginx Tool in Odoo. Please refer the blog below.

https://www.cybrosys.com/blog/how-to-configure-http-load-balancer-using-the-nginx-tool-in-odoo

Hope it helps