Seafile Pro behind reverse proxy, IP incorrect, ignoring X-FORWARDED-FOR

docker

#1

I have Seafile running (in docker) behind a reverse proxy. It is sending the X-FORWARDED-FOR header, however Seafile logs and shows the client IP as the reverse proxy IP.

Is there an option to honour the X-FORWARDED-FOR header?

Thanks


#2

Do you mean the Seafile Admin logs? It does work normally for me, see attachment. It does show the correct external client IPs.
I am using Apache as reverse proxy, but not using docker-version seafile however.


#3

Thanks for your reply! I’m running Caddy in front of the docker container. And you are right, I mean the Seafile Admin Logs. I can’t upload a screenshot for some reason. However where in your screenshots public IP’s are shown, I my case I only see the proxy server.