cloudfoundry-attic
Cannot talk to director at 'https://192.168.50.4:25555', please set correct target
Hello,
Trying deploy Bosh Lite, after execution
$ export no_proxy=xip.io,192.168.50.4 $ bosh target 192.168.50.4 lite
I receive this error:
Cannot talk to director at 'https://192.168.50.4:25555', please set correct target
How i can fix this?
Thanks
Which provider are you using? VirtualBox, AWS? With AWS, you'll probably be using different IPs.
If you haven't found it already, I'd recommend you use the newer bosh-lite deployment method documented at cloudfoundry/bosh-lite. It avoids the intermediate Vagrant tooling, can be reliably deployed across many IaaSes, and has recent versions of BOSH dependencies.
i think danny meant documented in cloudfoundry/bosh-deployment.
Sent from my iPhone
On Jun 28, 2017, at 5:27 PM, Danny Berger [email protected] wrote:
Which provider are you using? VirtualBox, AWS? With AWS, you'll probably be using different IPs.
If you haven't found it already, I'd recommend you use the newer bosh-lite deployment method documented at cloudfoundry/bosh-lite. It avoids the intermediate Vagrant tooling, can be reliably deployed across many IaaSes, and has recent versions of BOSH dependencies.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
@dpb587-pivotal i'm using VirtualBox. In fact, i'm trying to do nested virtualization, because i can't deploy the bosh-lite in my machine.
I had the same issue, and I'm on a linux host. For me, Virtualbox creates a virtual interface called vboxnet1 for bosh-lite. For some reason the interface is down after being created so it can't be reached. If you take it up using ifconfig <interface name> up then everything seems to work. I just ran into this today after updating Virtualbox (from 5.1.22 to 5.1.24) and vagrant (from 1.9.5 to 1.9.7).
EDIT: It was a virtualbox bug: https://www.virtualbox.org/ticket/16911
