When something goes wrong

Che Cloud Development Environments can encounter startup failures, performance issues, network errors, and configuration problems. Start by checking logs, then use the symptom-based sections in this guide to diagnose and resolve the issue.

The first step for any problem is to check the Cloud Development Environment logs. Logs capture IDE extension activity, container events, and process errors that point to the root cause.

Table 1. What problem are you experiencing?
Symptom	Description
Need to check logs	View logs from the CLI, the Kubernetes console, or the editor to identify errors and warnings.
Cloud Development Environment fails to start	Diagnose pod scheduling, image pull, DevWorkspace, and resource quota errors from the dashboard or operator logs.
Cloud Development Environment is slow	Identify configuration changes that reduce startup time and improve runtime performance.
Network connectivity issues	Diagnose WebSocket failures, proxy configuration problems, and DNS resolution errors.
OAuth or Git authentication errors	Verify callback URLs, Secret labels, GitLab scopes, and Bitbucket public keys.
Webview or editor UI errors	Fix service worker errors in private browsing windows.
Devfile syntax or validation errors	Diagnose component failures, lifecycle command problems, and volume or endpoint misconfigurations.