Disable X-forworded-for in ammune.ai

Disable X-forworded-for in ammune.ai

1.1 Disable x-forwarded-for in ammmune.ai In order to disable Ammune.ai from appending to the X-Forwarded-For header, the following line in the Nginx configuration. In Engines sever only (/home/l7admin/openresty/nginx/conf/l7http.conf) must be removed or commented out inside the container.
 sudo –i
 podman exec -it l7ammune_container /bin/bash
 nano /home/l7admin/openresty/nginx/conf/l7http.conf
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 nginx -s reload
 nginx -t

Using the current configuration, X-Forwarded-For (XFF) can be disabled for individual services as required. For permanently disabling XFF across all services, please follow the steps below:

1.2 Disable x-forwarded-for from start If X-Forwarded-For (XFF) needs to be disabled from the initial stage, it should be configured at the Ammune.ai Engine machines. Please ensure the required changes are applied at the engine level for the configuration to take effect.
The NginxConfigurator.py (Inside container - /home/l7admin/config/NginxConfigurator.py) file and disabling the following line: #ServerTextSection += '\n\t\t\tproxy_set_header X-Forwarded For $proxy_add_x_forwarded_for;\n'

You disable it by adding # in the start of the line
 sudo –i
 podman exec -it l7ammune_container /bin/bash
 nano /home/l7admin/config/NginxConfigurator.py
 Uncomment this line -#ServerTextSection += '\n\t\t\tproxy_set_header X-Forwarded For $proxy_add_x_forwarded_for;\n'
 nginx -s reload
 nginx -t
    • Related Articles

    • Disk Partition & Mounting Recommendation

      ammune.ai is mounted to /home/dbpost, so the only space required is there, as it will maintain logs and the encrypted database. We recommend a Single large partition: / (root) → 256GB (or as much as possible) Filesystem: xfs or ext4 This setup ...