Frequently Asked Questions

This topic provides guidance for common questions about running and configuring Pivotal Platform Dev.

Why do I receive a “Invalid SSL Cert” error?

When targeting your API with cf api, you may receive the following error:

Setting api endpoint to
Invalid SSL Cert for

Pivotal Platform Dev comes with a self-signed SSL certificate for its API. The self-signed SSL certificate causes an Invalid SSL Cert error when using the cf CLI.

To avoid the error:

  1. Start your Pivotal Platform Dev instance by running:

    cf dev start
  2. Run:

    cf api --skip-ssl-validation

How can I connect apps running in Pivotal Platform Dev to services running on my workstation?

Pivotal Platform Dev provides a special hostname for addressing the host from inside of app containers. If the Pivotal Platform Dev system domain is, then the host is routable at Services running on the host must be listening on all network interfaces for apps to access them, not just localhost.

Note: Using localhost inside of app containers does not refer to your workstation.

How can I customize the memory and CPU count used by Pivotal Platform Dev?

By default, Pivotal Platform Dev allocates 8 GB of memory to run.

To change the allocated memory:

  1. Navigate to your workspace.

  2. Run:

    cf dev start -m NEW-ALLOCATED-MEMORY

    Where NEW-ALLOCATED-MEMORY is the amount of memory you want to allocate in MB.

By default, Pivotal Platform Dev tries to use four cores. To change this setting:

  1. Navigate to your workspace.

  2. Run:

    cf dev start -c DESIRED-NUMBER-OF-CORES

    Where DESIRED-NUMBER-OF-CORES is the number of processor cores Pivotal Platform Dev should use.

How are App Security Groups (ASGs) configured in Pivotal Platform Dev?

Unlike Pivotal Platform, Pivotal Platform Dev allows apps to access all private address ranges without the need for additional ASGs. This is because Pivotal Platform Dev is considered a trusted, local environment.

To remove the all_pcfdev security group:

  1. Navigate to your app directory.

  2. Run:

    cf unbind-running-security-group all_pcfdev

Changes do not apply to existing running apps until you restart them.