Stay organized with collections
Save and categorize content based on your preferences.
This page describes known issues that you might encounter while using
Cloud Workstations.
Workbench failed to connect to server
This error indicates the editor is unable to establish a WebSocket connection to
the base editor. This is usually due to an intermediary
proxy or network configuration blocking WebSocket traffic, or blocking traffic
to *.cloudworkstations.dev domains.
If you aren't sure how to resolve the traffic issue, contact your network
administrator.
Disabling the Cloud Workstations API doesn't delete Cloud Workstations resources
Disabling the Cloud Workstations API doesn't delete Cloud Workstations resources.
To avoid being billed, you must delete the underlying Cloud Workstations
resources.
Environment variables set on the workstation configuration are not set in SSH sessions
Environment variable set at the workstation configuration or workstation level
are not set in the SSH sessions by default, and instead require the use of a
custom image.
If the gcloud CLI can't find your command, update to the current
version:
gcloudcomponentsupdate
Also, make sure that you use current Cloud Workstations gcloud CLI syntax.
For help, see
gcloud workstations --help.
As noted in the gcloud CLI
release levels, alpha and beta commands may change
without notice.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[],[],null,["# Known issues\n\nThis page describes known issues that you might encounter while using\nCloud Workstations.\n\nWorkbench failed to connect to server\n-------------------------------------\n\nThis error indicates the editor is unable to establish a WebSocket connection to\nthe base editor. This is usually due to an intermediary\nproxy or network configuration blocking WebSocket traffic, or blocking traffic\nto `*.cloudworkstations.dev` domains.\n\nIf you aren't sure how to resolve the traffic issue, contact your network\nadministrator.\n\nDisabling the Cloud Workstations API doesn't delete Cloud Workstations resources\n--------------------------------------------------------------------------------\n\nDisabling the Cloud Workstations API doesn't delete Cloud Workstations resources.\nTo avoid being billed, you must delete the underlying Cloud Workstations\nresources.\n\nEnvironment variables set on the workstation configuration are not set in SSH sessions\n--------------------------------------------------------------------------------------\n\nEnvironment variable set at the workstation configuration or workstation level\nare not set in the SSH sessions by default, and instead require the use of a\n[custom image](/workstations/docs/customize-container-images#container_image_that_sets_container_environment_variables_in_ssh_sessions).\n\nIntelliJ IDEA-based IDEs\n------------------------\n\nThe following features of the IntelliJ IDEA-based IDEs extension are\nnot available, due to\n[limitations on JetBrains Gateway](https://youtrack.jetbrains.com/issue/CWM-838/Editor-like-synchronization-for-consoles):\n\n- Debug on Kubernetes\n- Debug a locally running Cloud Run service\n\nGoogle Cloud CLI can't find my command\n--------------------------------------\n\nIf the `gcloud` CLI can't find your command, update to the current\nversion: \n\n gcloud components update\n\nAlso, make sure that you use current Cloud Workstations `gcloud` CLI syntax.\nFor help, see\n[`gcloud workstations --help`](/sdk/gcloud/reference/workstations).\nAs noted in the `gcloud` CLI\n[release levels](/sdk/gcloud#release_levels), alpha and beta commands may change\nwithout notice."]]
