Look at your cloud controller logs. You should see some reason for the 500 error. That should give you more clues as to why it's failing. Dan

'CF_TRACE=true cf login -u admin' produces the output below. What might the problem be? REQUEST: [2016-08-30T13:07:02-04:00] GET /v2/organizations?order-by=name HTTP/1.1 Host: api.example.com Accept:

Hey guys I know that maybe many of you still use nagios somewhere, so if you have deployments of nagios combined with AWS I have created a nagios plugin in golang to monitor Cloudwatch metrics that I

Hi Tom, I am working on this with Walid and we are using Bosh Lite. I tried running the command from the bosh lite VM but could not find a bin folder, so please advise?? thanks, -rania

Hi Tom, I am working Walid on this and I tried this but I don't see any bin folder from the bosh lite VM. Any Advise? thanks, -rania

Hey Josh, just trying to be a good open source citizen ;-) Greetings to the gang :) Cheers, Thomas

Hello Matt, thanks for the pointer - me stupid - was probably to late - works like a charm once I kill the cookie :) yay! Didn't expect the CF / Wildfly combo to be that smart by

Hi Walid, I assume you are working with bosh-lite, is that correct? If so, did you run "bin/add-route" script? That should add a route on your host OS to forward those traffic correctly to the VM.

We see an inconsistency in the behavior between CLI and v2 APIs and hence would like to understand the reasoning: 1. CLI command cf staging-security-groups expects the user to have admin role. This

OMG OMG Thomas! lol you're *so so* awesome buddy

I'd guess WildFly is setting JSESSIONID when first visiting the app, which would stick your browser session to the same app instance. thomas.darimont+github(a)gmail.com> wrote:

Hello group, this is my first post to this list so I hope I'm at the right place with my problem :) For a PCFDev demo at our Java User Group I wanted to deploy a Java EE App on Wildfly to Cloud

Hi Neil, You might want to just walk through the nginx control script manually and see if that leads you to the

From http://docs.cloudfoundry.org/deploying/common/vsphere-vcloud-cf-stub.html "Note: vSphere defaults to using an internal WebDAV blobstore for the Cloud Controller. " Then the spiff merge creates an

After installing the Virtual Box and get it up and running through the command vagrant up --provider=virtualbox and try to access it through bosh target 192.168.50.4 lite I keep getting the

Hi all, The CF Infrastructure team is working on bumping the version of etcd in etcd-release to the latest patch within the version 2 major line [0]. We've run into an issue [1] with the way that

Thanks. I've created a couple stories to address those two requests: https://www.pivotaltracker.com/story/show/129187415 https://www.pivotaltracker.com/story/show/129187421 As it stands, it might

How are CF hosts supposed to access the blobstore? If the bosh install assigns an IP to the blobstore vm one can't preconfigure DNS records. Yet the bosh deployment manifest for CF has a blobstore

While attempting to install CF on Vsphere the api_z1 server fails to deploy. Looking at the VM it appears that nginx fails to start. I see log entries of starting then dying immediately after. How can

This is great! We use the buildpack and fully support it being incubated. Thanks, Mike