Adding the RemoteIPValve (and adjusting the AccessLog valve) seems to have done the trick for me in 8.9.  Even though this page indicates it's for Datacenter only, it applies to Server as well, at least as of this comment: https://confluence.atlassian.com/jirakb/how-to-log-the-client-source-ip-in-access-logs-for-jira-data-center-978196913.html

i searched through a lot of internet sites. here finally i found the solution with the valve config. thanks dude! working fine now with nginx!

I see the comment that indicates that there are still problems when using nginx. However, I can confirm that things look good with Apache & JIRA v6.0.8

I have not tweaked server.xml to use RemoteIPValve.

I attach a screenshot that shows behaviour with Apache. I have also compared what things look like when rinetd is used as a forwarder... a bug in rinetd means that JIRA will never be able to show the client IP.

I had to use the 'RemoteIpValve' with JIRA 6.0.8, so I would not say it is fixed.

I use JIRA behind nginx with the following configuration for passing original request source:

			proxy_pass              http://localhost:8080;
			proxy_set_header        X-Real-IP $remote_addr;
			proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
			proxy_set_header	X-Forwarded-Proto $scheme;
			proxy_set_header        Host $http_host;
			proxy_http_version 	1.1;

this seems to be fixed in 6.0.6. However, haven't test this for any version prior to JIRA 6.0.6

Thanks David! It works for JIRA 4.4.4.

I've been testing RemoteIPValve

This seems to work...modify your server.xml and add this Valve after the <Engine> tag:

        <Engine name="Catalina" defaultHost="localhost">
 <Valve 
   className="org.apache.catalina.valves.RemoteIpValve"
   internalProxies="127\.0\.0\.1"
   remoteIpHeader="x-forwarded-for"
   remoteIpProxiesHeader="x-forwarded-by"
   protocolHeader="x-forwarded-proto"
   />
            <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true">

+1

+1 vote. I have a lot of user sessions where the user is logged as "Not available" and the inability to see the IP address means that I cannot see patterens... know if there is a problem or where the problem is originating. As it happens, there WAS a problem - someone was playing with JIRA CLI and managed to create scores of SOAP sessions. A fix to this issue would have told me the IP address (without any need to dig deep or look at any logs) and I could then have tracked down the culprit.

bump ...