You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Occasionally, you may run into scenarios where the agent is not able to connect.
330
-
This means the start script has failed.
324
+
Occasionally, you may run into scenarios where a workspace is created, but the agent is not connected. This means the agent or[init script](https://github.com/coder/coder/tree/main/provisionersdk/scripts) has failed on the resource.
331
325
332
326
```sh
333
327
$ coder ssh myworkspace
@@ -338,8 +332,8 @@ While troubleshooting steps vary by resource, here are some general best
338
332
practices:
339
333
340
334
- Ensure the resource has`curl` installed
341
-
- Ensure the resource canreach your Coder URL
342
-
- Manually connect to the resource (e.g.,`docker exec` or AWS console)
335
+
- Ensure the resource can`curl` your Coder[accessURL](./admin/configure.md#access-url)
336
+
- Manually connect to the resourceand check the agent logs(e.g.,`docker exec` or AWS console)
343
337
- The Coder agent logs are typically stored in`/var/log/coder-agent.log`
344
338
- The Coder agent startup script logs are typically stored in`/var/log/coder-startup-script.log`