Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Incorrect IP address used behind reverse proxy

I am using a dockerized version of Crowd which is sitting behind a Traefik reverse proxy.

Everything works fine except for one thing: I have a third party application that uses Crowd for identity management and I have added it as an application and added the external IP address of the third party application in the Remote Addresses tab.

However, Crowd blocks the authentication requests with this message:


>  INFO [crowd.manager.validation.ClientValidationManagerImpl] Client with address '' is forbidden from making requests to application 'x x x' is the IP address of the reverse proxy in the internal Docker network.

What changes do I have to make so that Crowd is able to know the original IP address? Is there a header that Traefik should set or something similar?


1 answer

0 votes
Daniel Eads Atlassian Team May 10, 2019

Hi Daniel,

Sounds like it's missing the X-Forwarded-For header. In nginx, we'd set it like this:

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

Traefik is new territory for me however! I see mention about Forwarded headers needing to have a trusted IP but am not completely sure that's what needs to happen in this situation. That's the path I'm headed down learning more about - just wanted to mention this in advance in case you might already have some knowledge in that area. If not, I will hopefully have some more info for you soon.


Hi Daniel,

thanks for the suggestions. tcpdump showed that the headers were present and correct. What was missing was to actually add traefik as a trusted proxy to Crowd :)



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events