If you are behind a corporate proxy or firewall, the gcloud command-line tool may not be able to access the internet with its default settings.
Installing Cloud SDK
The interactive Cloud SDK installers download components from the internet as part of the installation process, which may not work correctly if you are behind a proxy or firewall.
For a simpler installation process when proxy configuration is necessary, use one of the self-contained versioned archives to install the Cloud SDK. All previous versions of the Cloud SDK are also available to download from the downloads archive.
Once you have the SDK installed, proxy settings can be configured via Cloud SDK
properties by using the typical
gcloud config mechanism. For more information
on what Cloud SDK properties are and how to use them, refer to the
To start, set the type of proxy you are using and the address and port on which to reach it:
gcloud config set proxy/type [PROXY_TYPE] gcloud config set proxy/address [PROXY_IP_ADDRESS] gcloud config set proxy/port [PROXY_PORT]
- Cloud SDK supports the following values for
PROXY_IP_ADDRESSis the hostname or IP address of where the proxy can be reached.
PROXY_PORTis the port the proxy is running on (e.g.
For an authenticated proxy, you will need to set your proxy username and password using properties, like so:
gcloud config set proxy/username [USERNAME] gcloud config set proxy/password [PASSWORD]
Alternatively, to avoid having the proxy credentials recorded in any logs (such
as shell history or
gcloud logs) or in the gcloud CLI configuration file, you
can set the properties using environment variables, like so:
export CLOUDSDK_PROXY_USERNAME [USERNAME] export CLOUDSDK_PROXY_PASSWORD [PASSWORD]
The gcloud CLI won't store these values anywhere. This way, the credentials can be stored in an encrypted file locally, or they can be stored in a secure network location and retrieved when necessary.
If you are behind a proxy and you receive SSL handshake errors, it is likely that your proxy is a man-in-the-middle proxy which uses a custom CA. You need to set the following property to point to your custom CA file:
gcloud config set core/custom_ca_certs_file [PATH_TO_CUSTOM_CA]