The Remote Development feature for JetBrains IDEs is still in its active development stage, so that some issues may occur. This page is aimed to help you with an initial troubleshooting during the setup or later work.
Is there a difference between JetBrains Gateway from Toolbox, the one downloaded separately, or the one from an IDE?
Standalone JetBrains Gateway supports an option to "Open in IDE" your Space-based project If you don't use it, there are no other differences in installers and workflows.
Check the installation scenarios.
Can I point Remote Development to an existing IDE on my remote server? Is it possible to install IDE manually?
Since version 221.5481, you can manually register an existing backend IDE on the remote server and make it visible for JetBrains Gateway. Installed IDE will appear in the list of available builds:
The JetBrains Gateway installation itself doesn't finish successfully
Why does the SSH connection to a remote server fail during the setup?
JetBrains Gateway hangs on the Retrieving IDE versions step and doesn't load available IDEs
JetBrains Gateway tries to connect but fails. Credentials are 100% correct.
I select an IDE installer from the local machine, but the process of uploading fails
Upload of remote-dev-worker fails with "exit code: 139 (SIGSEGV)"
If your remote machine's OS is RHEL, CentOS, RockyLinux - check syslog for SELinux warnings or disable SELinux and retry installation
On local machine, process fails with the "Failed to download JetBrains Client" error
Your local computer must have a network connection to the following JetBrains URLs:
Alternatively, you can configure the fully offline mode.
Work with remote project
Failed to get IDE status in 60 seconds. Probably IDE backend is stuck
CPU or resources usage looks abnormal
IDE hangs and doesn't respond
The remote IDE worked but stopped responding
Collecting logs and submitting reports
If the solutions above don't help, and you need our assistance, please provide a detailed description. Besides the IDE version, logs, and thread dumps, which are a must, we appreciate a code/project sample, screenshot, or screencast/gif that illustrates the problem.
Attach them to your issue when submitting a report.
To make the issue visible only to the JetBrains team, you can set its visibility to the jetbrains-team group. With the exception of images, all attachments are visible only to the JetBrains team by default.
Collect logs from UI
From JetBrains Gateway: Welcome (start) screen - left bottom corner - gear icon - "Collect All Logs".
From the main IDE you use as Remote Development starting point: top menu - "Help" - "Collect Logs and Diagnostic Data".
From launched JetBrains Client session (connected to your remote server): top menu - "Help" - "Collect Host and Client Logs"
Collect logs manually
On local workstation side: the location depends on the OS of your local computer.
We recommend collecting and sending the whole logs' folder from directories used by the IDE.
On the remote server: logs are located per-project in the IDE installation folder.
Default installation path is