Skip to content
This repository was archived by the owner on Nov 16, 2020. It is now read-only.

Unable to use through a proxy #5

Closed
mUbsta opened this issue Dec 12, 2017 · 1 comment
Closed

Unable to use through a proxy #5

mUbsta opened this issue Dec 12, 2017 · 1 comment

Comments

@mUbsta
Copy link

mUbsta commented Dec 12, 2017

Is there any way to get this working via a proxy?

2017-12-12 14:52:04.331 [debug] <0.193.0> Fetched EC2 instance ID from "http://169.254.169.254/latest/meta-data/instance-id": "<removed>" 2017-12-12 14:52:09.331 [error] <0.192.0> CRASH REPORT Process <0.192.0> with 0 neighbours exited with reason: {timeout,{gen_server,call,[rabbitmq_aws,{request,"autoscaling",get,[],"/?Action=DescribeAutoScalingInstances&Version=2011-01-01",[],[],undefined}]}} in application_master:init/4 line 134 2017-12-12 14:52:09.332 [info] <0.33.0> Application rabbit exited with reason: {timeout,{gen_server,call,[rabbitmq_aws,{request,"autoscaling",get,[],"/?Action=DescribeAutoScalingInstances&Version=2011-01-01",[],[],undefined}]}}

We have set cluster_formation.proxy.https_proxy in rabbitmq.conf however is looks like this is still trying to connect directly to autoscaling.<awsregion>.amazonaws.com

@lukebakken
Copy link
Contributor

Hello @mUbsta -

Please use the mailing list to ask questions. The RabbitMQ team does not use GitHub issues for issue analysis.

When you post this question to the mailing list, please include version information for RabbitMQ, Erlang and the plugins you are using. Please provide your complete configuration file as well.

Thanks -
Luke

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants