Separate proxy settings for inter-node communication #4392
Closed
Comments
No, that's currently not possible but it sounds like a good idea. |
|
Without proxy settings the threatintel feature is unusable in a multihost GL setup so in my opinion it's a bug. |
bernd
added a commit
that referenced
this issue
Jul 13, 2018
This can be used to bypass a configured proxy server for a list of hostnames or IP addresses. It must be used if the inter-node communication between graylog servers should not go through a configured proxy server. The matcher implementation for the "http_non_proxy_hosts" is similar to the implementation that is used for the "http.nonProxyHosts" system property. (only the delimiter is "," instead of "|" for consistency) By using a similar implementation, it will be possible to also set the system property in the future. (if needed - tbd) Fixes #4905 Fixes #4392
kroepke
added a commit
that referenced
this issue
Jul 16, 2018
This can be used to bypass a configured proxy server for a list of hostnames or IP addresses. It must be used if the inter-node communication between graylog servers should not go through a configured proxy server. The matcher implementation for the "http_non_proxy_hosts" is similar to the implementation that is used for the "http.nonProxyHosts" system property. (only the delimiter is "," instead of "|" for consistency) By using a similar implementation, it will be possible to also set the system property in the future. (if needed - tbd) Fixes #4905 Fixes #4392 (This needs to be cherry-picked into 2.4 once merged)
bernd
added a commit
that referenced
this issue
Jul 16, 2018
This can be used to bypass a configured proxy server for a list of hostnames or IP addresses. It must be used if the inter-node communication between graylog servers should not go through a configured proxy server. The matcher implementation for the "http_non_proxy_hosts" is similar to the implementation that is used for the "http.nonProxyHosts" system property. (only the delimiter is "," instead of "|" for consistency) By using a similar implementation, it will be possible to also set the system property in the future. (if needed - tbd) Fixes #4905 Fixes #4392 (cherry picked from commit 979787e)
bernd
added a commit
that referenced
this issue
Jul 16, 2018
This can be used to bypass a configured proxy server for a list of hostnames or IP addresses. It must be used if the inter-node communication between graylog servers should not go through a configured proxy server. The matcher implementation for the "http_non_proxy_hosts" is similar to the implementation that is used for the "http.nonProxyHosts" system property. (only the delimiter is "," instead of "|" for consistency) By using a similar implementation, it will be possible to also set the system property in the future. (if needed - tbd) Fixes #4905 Fixes #4392 (cherry picked from commit 979787e)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @jekelundh on December 4, 2017 9:39
When http_proxy is set the GL-nodes tries to connect to each other using proxy meaning everything goes offline.
Is there a way to set nonProxyHost in the "http_proxy" setting ?
Running GL graylog-server-2.4.0-4.beta.2 (with embeddded threatintel plugin)
Env is Centos 7 with java 1.8.0_151-b12
Copied from original issue: Graylog2/graylog-plugin-threatintel#74
The text was updated successfully, but these errors were encountered: