Skip to content

Commit b5274e2

Browse files
committed
doc: debugging and reporting issues
Document how to configure the debug level before reporting any Coder plugin issue and also how to collect or view the Toolbox log files
1 parent 79cb627 commit b5274e2

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed

README.md

+36
Original file line numberDiff line numberDiff line change
@@ -137,6 +137,42 @@ mitmproxy can do HTTP and SOCKS5 proxying. To configure one or the other:
137137
5. Before authenticating to the Coder deployment we need to tell the plugin where can we find mitmproxy
138138
certificates. In Coder's Settings page, set the `TLS CA path` to `~/.mitmproxy/mitmproxy-ca-cert.pem`
139139

140+
## Debugging and Reporting issues
141+
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
144+
and command execution, which is not visible at the default log level.
145+
146+
If you encounter a problem with Coder's JetBrains Toolbox plugin, follow the steps below to gather more
147+
information and help us diagnose and resolve it quickly.
148+
149+
### Enable Debug Logging 🔍
150+
151+
To help with troubleshooting or to gain more insight into the behavior of the plugin and the SSH connection to
152+
the workspace, you can increase the log level to _DEBUG_.
153+
154+
Steps to Enable Debug Logging:
155+
156+
1. Open Toolbox
157+
158+
2. Navigate to the Toolbox App Menu (hexagonal menu icon) > Settings > Advanced.
159+
160+
3. In the screen that appears, select _DEBUG_ for the `Log level:` section.
161+
162+
4. Hit the back button at the top.
163+
164+
There is no need to restart Toolbox, as it will begin logging at the DEBUG level right away.
165+
166+
⚠️ Toolbox does not persist log level configuration between restarts.
167+
168+
#### Viewing the Logs
169+
170+
Once enabled, debug logs will be written to the Toolbox log files. You can access logs directly
171+
via Toolbox App Menu > About > Show log files.
172+
173+
Alternatively, you can generate a ZIP file using the Workspace Action Menu, available either on the main
174+
Workspaces page in Coder or within the individual workspace view, under the option labeled _Collect logs_.
175+
140176
## Releasing
141177

142178
1. Check that the changelog lists all the important changes.

0 commit comments

Comments
 (0)