How to identify multiple IPs in JIRA application logs
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
This how to guide explains what the multiple IPs referenced in the JIRA application logs refer to. For example:
1
2016-03-25 10:35:13,626 http-nio-8080-exec-22 ERROR captain-planet 635x404x1 7nuhc0 131.103.28.11,10.0.1.83 /secure/Dashboard.jspa [c.a.g.r.internal.http.HttpClientFetcher] Unable to retrieve responseSolution
This is a set of IP addresses that may include the proxy forwarded address - this comes from the X-Forwarded-For header.
Otherwise it includes the remote IP address, which is the IP address of the client or last proxy that sent the request.
It can also be null if neither of those exist.
In this example,
131.103.28.11is from theX-Forwarded-Forheader, and10.0.1.83is the remote IP address.
Was this helpful?