I've used TCP/8080 but with a TLS listener as a work-around for this issue. It wasn't ideal, but it solved the problem and we had limited options as TCP/8080 was one of the few egress ports allowed.

Hi Amit Thanks for your reply… Now I could combine all the jobs of cf-231 into one vm, but blobstore process alone shows the following error: 2016/04/26 11:04:29 [emerg] 23408#0: listen() to

Hi Check with 8080 port Pls let me know is it https u r using as the port mentioned is secure one In addition u can use Soap port in the protocol and port range definition Other option is to use

Hi Shannon, Same problem statement and solution/workaround here. Changing such a corporate setup usually is much more time consuming (if successful at all) compared to the changes in CF setup as you

I'm not sure of your precise use cases, but I'd suggest looking into the implementation of Tasks [1] based on the v3 cloud controller api [2]. With tasks you can spin up containers on the fly fairly

An simple servlet can reproduce my problem on standard bosh lite CF. 1. push to the app the bosh lite cf push test -p ./test.war 2. access the servlet deployed on CF wget

Hi CLI users, With apps deployed to DEAs, a health check is performed at application start-up targeting the app's port, unless you specified `--no-route`, in which case the process is monitored. With

Following up on this thread, we plan on spending some time this week to discuss the functionality of the Binary Service Broker. If you have any additional feedback regarding the project we urge you to

The problem right now is that the buildpack names are no longer available during staging. All the code is available (because the stager needs to call `bin/detect` for each buildpack in turn), but it

I'm interested to hear from operators how you're supporting websockets for CF on AWS, both for user tailing of app logs from Loggregator, and for apps running on CF that take websocket

Separate VM not necessary, you need a consul server cluster though, can't just have consul agents in client mode. Your server cluster can be colocated with other VMs, and the servers can act as

What does that mean?

Forgot to mention that I collocated consul_agent with api_worker and also enabled it in server mode and removed it as a separate vm. Even after this, the consul_agent process was not coming up in

Hi Amit Pls let me know if consul as a separate vm is necessary for cf-231 deployment, though we collocate consul_agent in every other job of cf-231 Regards Nithiyasri Sent: Monday, April 25, 2016

Hello, Has anyone implemented or know of an implementation similar to that of "AWS Lambda" using Cloud Foundry? The idea is to have the ability to run small scripts on the fly without having a

Thanks Shawn. We appreciate the feedback and will take it into account before making any decisions that will remove the functionality.

Your first job has consul services, so you'll need to colocate the consul_agent there too. You also don't have any consul servers running anywhere. TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>

Actually one CF instance is bosh lite one deployed on AWS, I didn't change things related to haproxy. I also can reproduce it on this bosh lite instance. - default_networks: - name: cf1

Pls change the lookup location and it work's -- Thanks & Regards Sunil Babu K C +91-81970-35608

Hi Amit I am using cf-231 release. In the spiff generated yml, I could combine api_worker and cloud_controller jobs into one, dea-spare with router. But when I remove consul as a separate VM and