search

cloudfoundry-attic / bosh-lite

A lite development env for BOSH
Apache License 2.0
319 stars 245 forks source link

Cannot talk to director at 'https://192.168.50.4:25555', please set correct target #431

Open joaocavajo opened 7 years ago

joaocavajo commented 7 years ago

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

dpb587-pivotal commented 7 years ago

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.

cppforlife commented 7 years ago

i think danny meant documented in cloudfoundry/bosh-deployment.

Sent from my iPhone

On Jun 28, 2017, at 5:27 PM, Danny Berger notifications@github.com 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.

joaocavajo commented 7 years ago

@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.

griffingarland commented 7 years ago

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