> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/ams/v3.0/help-and-support/application-help-pages/app-configuration/ip-address-detection-page.md). # IP Address detection configuration page ![](https://1500666603-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzPrDxVWpXXpSNTpkDVnR%2Fuploads%2Fgit-blob-9fc5658800af9d334189f4360f0dd8d39097fc6a%2Fui-page-ip-detection.png?alt=media) ## Proxy settings If you place AMS behind a reverse proxy or load balancer, you'll need to configure AMS to correctly find the real client IP address from the X-Forwarded-For header. This will ensure that rate limiting and audit logging are working against the correct IP. #### Resolve client IP address from X-Forwarded-For headers Indicates that the client IP address should be extracted from the X-Forwarded-For headers. If this setting is off, the client IP address is determined from the IP address of the machine that connects to the AMS service. #### Maximum allowed entries in the header The X-Forward-For header can be set by the client, and therefore can be spoofed. If you have a single load balancer or proxy in front of the AMS service, then set this to `1`. This indicates that only the first entry in the X-Forwarded-For header should be used, and the others ignored. #### Known proxy IP addresses If you know the IP addresses of your proxy servers, you can add them here. AMS will use the IP address in the X-Forwarded-For header that appears after these known IP addresses. #### Known proxy networks If you know the network range that your proxy servers live in, you can use that instead of individual IPs. Any IP addresses in these ranges will be treated as trusted proxy addresses when resolving the real client IP. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lithnet.io/ams/v3.0/help-and-support/application-help-pages/app-configuration/ip-address-detection-page.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.