@@ -101,6 +101,13 @@ If `ide_product_code` and `ide_build_number` is missing, Toolbox will only open
101
101
page. Coder Toolbox will attempt to start the workspace if it’s not already running; however, for the most reliable
102
102
experience, it’s recommended to ensure the workspace is running prior to initiating the connection.
103
103
104
+ > ⚠️ Note: ` folder ` should point to a remote IDEA project that has already been opened and appears in the ` Projects `
105
+ > tab.
106
+ > If the path refers to a project that doesn't exist, the remote IDE won’t start or load it.
107
+
108
+ > Until [ TBX-14952] ( https://youtrack.jetbrains.com/issue/TBX-14952/ ) is fixed, it's best to either use a path to a
109
+ > previously opened project or leave it empty.
110
+
104
111
## Configuring and Testing workspace polling with HTTP & SOCKS5 Proxy
105
112
106
113
This section explains how to set up a local proxy (without authentication which is not yet supported) and verify that
@@ -139,11 +146,11 @@ mitmproxy can do HTTP and SOCKS5 proxying. To configure one or the other:
139
146
140
147
## Debugging and Reporting issues
141
148
142
- Enabling debug logging is essential for diagnosing issues with the Toolbox plugin, especially when SSH
143
- connections to the remote environment fail — it provides detailed output that includes SSH negotiation
149
+ Enabling debug logging is essential for diagnosing issues with the Toolbox plugin, especially when SSH
150
+ connections to the remote environment fail — it provides detailed output that includes SSH negotiation
144
151
and command execution, which is not visible at the default log level.
145
152
146
- If you encounter a problem with Coder's JetBrains Toolbox plugin, follow the steps below to gather more
153
+ If you encounter a problem with Coder's JetBrains Toolbox plugin, follow the steps below to gather more
147
154
information and help us diagnose and resolve it quickly.
148
155
149
156
### Enable Debug Logging
@@ -159,46 +166,48 @@ Steps to enable debug logging:
159
166
160
167
3 . In the screen that appears, select _ DEBUG_ for the ` Log level: ` section.
161
168
162
- 4 . Hit the back button at the top.
169
+ 4 . Hit the back button at the top.
163
170
164
171
There is no need to restart Toolbox, as it will begin logging at the __ DEBUG__ level right away.
165
172
166
173
> ⚠️ ** Attention:** Toolbox does not persist log level configuration between restarts.
167
174
168
175
#### Viewing the Logs
169
176
170
- Once enabled, debug logs will be written to the Toolbox log files. You can access logs directly
177
+ Once enabled, debug logs will be written to the Toolbox log files. You can access logs directly
171
178
via Toolbox App Menu > About > Show log files.
172
179
173
- Alternatively, you can generate a ZIP file using the Workspace action menu, available either on the main
180
+ Alternatively, you can generate a ZIP file using the Workspace action menu, available either on the main
174
181
Workspaces page in Coder or within the individual workspace view, under the option labeled _ Collect logs_ .
175
182
176
183
## Coder Settings
177
184
178
185
The Coder Settings allows users to control CLI download behavior, SSH configuration, TLS parameters, and data
179
186
storage paths. The options can be configured from the plugin's main Workspaces page > deployment action menu > Settings.
180
187
181
- ### CLI related settings
188
+ ### CLI related settings
182
189
183
190
``` Binary source ``` specifies the source URL or relative path from which the Coder CLI should be downloaded.
184
191
If a relative path is provided, it is resolved against the deployment domain.
185
192
186
193
``` Enable downloads ``` allows automatic downloading of the CLI if the current version is missing or outdated.
187
194
188
- ``` Binary directory ``` specifies the directory where CLI binaries are stored. If omitted, it defaults to the data directory.
195
+ ``` Binary directory ``` specifies the directory where CLI binaries are stored. If omitted, it defaults to the data
196
+ directory.
189
197
190
198
``` Enable binary directory fallback ``` if enabled, falls back to the data directory when the specified binary
191
199
directory is not writable.
192
200
193
- ``` Data directory ``` directory where plugin-specific data such as session tokens and binaries are stored if not
201
+ ``` Data directory ``` directory where plugin-specific data such as session tokens and binaries are stored if not
194
202
overridden by the binary directory setting.
195
203
196
204
``` Header command ``` command that outputs additional HTTP headers. Each line of output must be in the format key=value.
197
205
The environment variable CODER_URL will be available to the command process.
198
206
199
207
### TLS settings
200
208
201
- The following options control the secure communication behavior of the plugin with Coder deployment and its available API.
209
+ The following options control the secure communication behavior of the plugin with Coder deployment and its available
210
+ API.
202
211
203
212
``` TLS cert path ``` path to a client certificate file for TLS authentication with Coder deployment.
204
213
The certificate should be in X.509 PEM format.
@@ -210,7 +219,7 @@ The certificate should be in X.509 PEM format.
210
219
certs returned by the Coder deployment. The file should be in X.509 PEM format. This option can also be used to verify
211
220
proxy certificates.
212
221
213
- ``` TLS alternate hostname ``` overrides the hostname used in TLS verification. This is useful when the hostname
222
+ ``` TLS alternate hostname ``` overrides the hostname used in TLS verification. This is useful when the hostname
214
223
used to connect to the Coder deployment does not match the hostname in the TLS certificate.
215
224
216
225
### SSH settings
@@ -227,11 +236,13 @@ rules for matching multiple workspaces.
227
236
228
237
``` SSH network metrics directory ``` directory where network information used by the SSH proxy is stored.
229
238
230
- ``` Extra SSH options ``` additional options appended to the SSH configuration. Can be used to customize the behavior of SSH connections.
239
+ ``` Extra SSH options ``` additional options appended to the SSH configuration. Can be used to customize the behavior of
240
+ SSH connections.
231
241
232
242
### Saving Changes
233
243
234
- Changes made in the settings page are saved by clicking the Save button. Some changes, like toggling SSH wildcard support,
244
+ Changes made in the settings page are saved by clicking the Save button. Some changes, like toggling SSH wildcard
245
+ support,
235
246
may trigger regeneration of SSH configurations.
236
247
237
248
### Security considerations
0 commit comments