How to locate the source file where NO_PROXY is set

Applicability

Description

When trouble shooting with connection issues, usually users will check NO_PROXY configured in SOAR global environment variables or individual asset environment variables.

Set global environment variables

Configure proxies for a Splunk SOAR (On-premises) asset

However, some users may forgot that they have NO_PROXY configured in linux too.

Investigation

Login the ssh session as phantom user and run command below to check if there is NO_PROXY configured in linux:

$ printenv

In case there is NO_PROXY or no_proxy environment variable, run commands below to locate the source file where the "NO_PROXY" is set.

# User-specific configuration files
grep -i 'NO_PROXY' ~/.bashrc ~/.bash_profile ~/.profile ~/.bash_logout# System-wide configuration files
grep -i 'NO_PROXY' /etc/environment /etc/profile /etc/bash.bashrc# Custom scripts in /etc/profile.d/
grep -i 'NO_PROXY' /etc/profile.d/*# Service configuration files (if applicable)
grep -i 'NO_PROXY' /etc/systemd/system/*.service /etc/init.d/*

Resolution

If possible, remove NO_PROXY in Linux to avoid duplication and conflicts.

User may have special reason to have NO_PROXY configured in Linux, then make sure the configuration is correct. And user need to be aware of that the SOAR configuration for NO_PROXY is not effective since OS level take precedence over SOAR-specific settings.