It shows all good. I can ssh into the api machine with no problems.


└─>bosh vms
Acting as user 'admin' on 'Bosh Lite Director'
Deployment `cf-warden'

Director task 18

Task 18 done


+------------------------------------+---------+---------------+--------------+
| Job/index | State | Resource Pool | IPs
|

+------------------------------------+---------+---------------+--------------+
| api_z1/0 | running | large_z1 |
10.244.0.134 |
| doppler_z1/0 | running | medium_z1 |
10.244.0.142 |
| etcd_z1/0 | running | medium_z1 |
10.244.0.42 |
| ha_proxy_z1/0 | running | router_z1 |
10.244.0.34 |
| hm9000_z1/0 | running | medium_z1 |
10.244.0.138 |
| loggregator_trafficcontroller_z1/0 | running | small_z1 |
10.244.0.146 |
| nats_z1/0 | running | medium_z1 |
10.244.0.6 |
| postgres_z1/0 | running | medium_z1 |
10.244.0.30 |
| router_z1/0 | running | router_z1 |
10.244.0.22 |
| runner_z1/0 | running | runner_z1 |
10.244.0.26 |
| uaa_z1/0 | running | medium_z1 |
10.244.0.130 |

+------------------------------------+---------+---------------+--------------+

VMs total: 11

On Aug 25, 2015, at 14:15, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote:

what does your `bosh vms` show?

On Tue, Aug 25, 2015 at 10:21 AM, kris rice <kris.rice(a)jokr.net> wrote:

Seems a combination of the 215 release and the patches Vbox let’s me
finally have a setup running more than ~10 minutes. So I have a clean
install from this morning. Now I get a connection refused

└─>cf api https://api.10.244.0.134.xip.io/
Setting api endpoint to https://api.10.244.0.134.xip.io/.
<https://api.10.244.0.134.xip.io/>..
FAILED
Error performing request: Get https://api.10.244.0.134.xip.io/v2/info:
dial tcp 10.244.0.134:443: connection refused


I added the route changes and verified the traceroute is going to the
proper place thru the vbox.

Any suggestions to check on ?

-kris