You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies if I've missed something, I'm a novice Github user. I have a Graylog 5.0.8 server deployed inside AWS on an EC2 instance, in a "private" subnet.
I have a Squid proxy in the "public" subnet and I can see traffic going from Graylog through the proxy, having set the http_proxy_uri variable in the server.conf.
However, even though I've checked the "use HTTP proxy" box in the AWS plugin config, it does not seem to do so. When trying to add a new input, when it attempts to connect to Kinesis, I can see from Wireshark that the connection attempt goes straight to Kinesis's public endpoint, not via my proxy.
So it looks to me (and I may be wrong, I am not an expert!) that it does not seem to be "respecting" the configuration to use the proxy.
Many thanks in advance!
IanM
The text was updated successfully, but these errors were encountered:
Hi there,
Apologies if I've missed something, I'm a novice Github user. I have a Graylog 5.0.8 server deployed inside AWS on an EC2 instance, in a "private" subnet.
I have a Squid proxy in the "public" subnet and I can see traffic going from Graylog through the proxy, having set the http_proxy_uri variable in the server.conf.
However, even though I've checked the "use HTTP proxy" box in the AWS plugin config, it does not seem to do so. When trying to add a new input, when it attempts to connect to Kinesis, I can see from Wireshark that the connection attempt goes straight to Kinesis's public endpoint, not via my proxy.
So it looks to me (and I may be wrong, I am not an expert!) that it does not seem to be "respecting" the configuration to use the proxy.
Many thanks in advance!
IanM
The text was updated successfully, but these errors were encountered: