-
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
Example Vagrant file doesn't work out of the box: Error querying node status: Get http://127.0.0.1:4646/v1/nodes: dial tcp 127.0.0.1:4646: connect: connection refused
#113
Comments
Part of the problem, although I am not sure how to fix it. It looks like nomad is listening on the wrong IP address.
|
I have since moved on from the example Vagrantfile (I will post my setup soon). I suffered from exactly the same issue though and some changes I made helped... Ansible Role Variables: |
In the following repo (https://github.com/dnk8n/monitored-orchestration/tree/main/dev) you can find a Vagrantfile that uses both ansible-nomad and ansible-consul to spin up a dev cluster. You might want to reconfigure the VM resources to suit you. In it I follow some of the suggestions I make to work around the problem of this issue. I tried to get away from needing to have Not sure if all the modifications were necessary. Often had to totally destroy and re- I tested with The UI endpoints are: nomad: consul: |
The text was updated successfully, but these errors were encountered: