Hi all, We've recently announced CF Summit events for both Berlin and Shanghai, and we'd love your participation! Berlin will be on November 2nd and 3rd, 2015 > http://berlin2015.cfsummit.com/ The

Hi, sorry for the slow reply. Could you give us some more details. Can you try logging in with the CF_TRACE=true environment variable set to see what requests are being made and give us the output

perhaps this makes sense as a github issue? wayneeseguin(a)starkandwayne.com> wrote: -- Thank you, James Bayer

Hi Discussions, I'd like to add you to my professional network on LinkedIn. - Sean Confirm that you know Sean:

bump wrote:

Hi All, I have installed the Cloud Foundry v202 on vSphere. Now, if I try to see the VMs list it gives the HTTP 500 Error.. Is there any problem with CF Version or I need to make a change

Although unrelated to instance type, I don't see an availability zone listed for the resource pool - perhaps that's something to check? And double check subnet, IP ranges, and AZ are all correctly

Unfortunately the employees are behind a firewall that only allows egress 80 and 443; they don't have a particular dislike to 4443. They dislike all of the ports :) wrote:

I use t2.micro stemcells all the time, but I only deploy with bosh-init, not bosh. here's a snippet

Point being: If you want or need to keep 443 as HTTPS, perhaps you can find another allowed egress port and move wss there. From: sushiandbeer(a)outlook.com To:

I ran into the same issue. My solution was to run wss on 8080. Yes, it's weird to run SSL on 8080, but it was allowed out the firewall. Date: Wed, 19 Aug 2015 22:30:03 -0700 From:

Why not try with latest version of that stemcell? https://bosh.io/stemcells/bosh-aws-xen-hvm-ubuntu-trusty-go_agent ( 3048 ) In list of versions, no release notes... I wonder why it has "light" in

Right. t2 series do not have ephemeral disks and that's why you have to add ephemeral disk configuration in cloud_properties, but DrNic's error seems to happen earlier than creation of a VM.

Can you try adding an ephemeral disk? We had issues before with HVM instances that have no default ephemeral disk... Here is our

Hmm, tried t2.small and it failed too as above. My manifest is https://gist.github.com/drnic/0ee3335b0c0d435861e6 - anything you can spot I'm missing? Thanks for the help. wrote: -- Dr Nic

t2.micro was what I tried and it failed

We are deploying to t2.smalls and it works fine.... Is it just in t2.micros that it fails? wrote:

I wanted a cheap AWS vm for our VPC so I tried using t2.micro. I was using HVM stemcell. But I get the following AWS error: Started creating bound missing vms > small_z1/0. Failed: The

the x-forwarded-proto header is pretty important for large public clouds as most of them enable http and https that i'm aware of. in this situation, i'm not sure how we forego the header when it's

With SSL instead of HTTPS you lose the X-Forwarded headers which would be needed for the apps to know if the traffic came in as secure, which would only be an issue if you're allowing both 80 and 443