-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always tries to connect to 127.0.0.1:8500 #65
Comments
The only reference (apart from utils/config_seeder.js) on |
I've tried all 3. And |
Here's the rest of the {"stack":"Error: connect ECONNREFUSED 127.0.0.1:8500\n at Object.exports._errnoException (util.js:874:11)\n at exports._exceptionWithHostPort (util.js:897:20)\n at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1063:14)","code":"ECONNREFUSED"},"msg":"connect ECONNREFUSED 127.0.0.1:8500","time":"2016-03-21T15:30:23.604Z","v":0} Maybe the problem is on my end. Still investigating... |
127.0.0.1 is coming from the consul lib. When it's required here, |
Is it because index.js is requiring config_seeder.js and config_reader.js before the variables are being set? |
Yes. Happened in d89f571 |
Going to issue a patch for that, thanks for the report! |
Great, thanks! |
This should be patched on v0.12.8 now. |
@cleung2010 thanks, works now! |
This seems to be a recent problem. When I run git2consul, regardless of my
endpoint
config, it's trying to hit127.0.0.1:8500
for some reason:I'm running latest. Verified
global.endpoint
is correct by logging it.The text was updated successfully, but these errors were encountered: