Infos:
- Used Zammad version: 2.5.x
- Used Zammad installation source: (source, package, …) apt
- Operating system: ubuntu 16.04.4 64 bit
- Browser + version: chrome 67
Expected behavior:
- show the real client ip
Actual behavior:
- always uses 127.0.0.1
Steps to reproduce the behavior:
- install zammad, and log in from the local network (private subnets)
installed everything like the documentation says
nginx conf:
upstream zammad-railsserver {
server localhost:3000;
}
upstream zammad-websocket {
server localhost:6042;
}
server {
listen 80;
# replace 'localhost' with your fqdn if you want to use zammad from remote
server_name zammad.int.example.org;
root /opt/zammad/public;
access_log /var/log/nginx/zammad.access.log;
error_log /var/log/nginx/zammad.error.log;
client_max_body_size 50M;
location ~ ^/(assets/|robots.txt|humans.txt|favicon.ico) {
expires max;
}
location /ws {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header CLIENT_IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_read_timeout 86400;
proxy_pass http://zammad-websocket;
}
location / {
proxy_set_header Host $http_host;
proxy_set_header CLIENT_IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_read_timeout 300;
proxy_pass http://zammad-railsserver;
gzip on;
gzip_types text/plain text/xml text/css image/svg+xml application/javascript application/x-javascript application/json application/xml;
gzip_proxied any;
}
}
in /var/log/nginx/zammad.access.log are the real ip’s, so it seems to be a zammad problem.
