Hi All, wanted to check someone has faced this issue before and can help us. We are trying to exempt multiple URLs to go via proxy using no_proxy config paramter in proxy.yaml.
However it works for one host i.e. we can only exempt one host from going via proxy.
Below configuration is expected to exempt both host1 and host2 from going via proxy, however it doesnt exempt any of them. Connections to both of them are going via proxy URL only. no_proxy: <host1>|<host2>
When we define only one host1 in the no_proxy parameter, it works fine for one host1 entry.
no_proxy: <host1>
Also I tried by giving comma as I find out in an article that for CURL it is asking , but then both hosts are not responding.
The SailPoint configuration does require the pipe separation. In addition, this is case sensitive.
Have you tried using no_proxy:<host2> and validated that this host is working alone? This will help isolate whether it is an issue with the multiple hosts configuration or the second host itself.
As in the above article I have highlighted that using | as well as , it is not taking. I have tried both and already went through the article that you have sent but not working for me.
While I am trying to CURL the API it is giving as expected result along with response. But while test connection only it is working for single application another one is giving timeout error.
Hi @suraj_gorle , can you check docker.env and /etc/profile.env files in your environment. Is no_proxy under these files updated for multiple URLs? Please do not edit these files, they are auto-generated.
After that you can also check the environment variables set on the VA using below command
Hi @shaileeM, rebooted but still same response. Also after rebooting on welcome page it is returning the command not found for the 2nd hostname after pipe(|).
Thanks Suraj, at some stage during our troubleshooting, we faced the same issue.
Now I suggest to open a support case and upload the charon and stunt logs to debug.
In our case, we had noticed that VA was unable to connect to certain required AWS services due to which docker.env wasn’t getting created and causing the issue.
You might have a similar issue.
Another thing I want to suggest is , you can try the following :
Export the no_proxy parameter manually using following command :
Hi @shaileeM , Thanks for the suggestion.
I have tried to export the no_proxy with pipe(|) it is not taking. It is saying command not found kind of error.
After that I have tried with comma(,) it is taking. It will cause any issue for us ?
Thank you.