@@ -19,13 +19,13 @@ string `OK`.
19
19
20
20
If there is an issue, you may see one of the following errors reported:
21
21
22
- ### < a name = " EACS01 " >EACS01 : Access URL not set</ a >
22
+ ### EACS01: Access URL not set
23
23
24
24
** Problem:** no access URL has been configured.
25
25
26
26
** Solution:** configure an [ access URL] ( ./configure.md#access-url ) for Coder.
27
27
28
- ### < a name = " EACS02 " >EACS02 : Access URL invalid</ a >
28
+ ### EACS02: Access URL invalid
29
29
30
30
** Problem:** ` ${CODER_ACCESS_URL}/healthz ` is not a valid URL.
31
31
@@ -35,7 +35,7 @@ If there is an issue, you may see one of the following errors reported:
35
35
36
36
> ** Tip:** You can check this [ here] ( https://go.dev/play/p/CabcJZyTwt9 ) .
37
37
38
- ### < a name = " EACS03 " >EACS03 : Failed to fetch ` /healthz ` </ a >
38
+ ### EACS03: Failed to fetch ` /healthz `
39
39
40
40
** Problem:** Coder was unable to execute a GET request to
41
41
` ${CODER_ACCESS_URL}/healthz ` .
@@ -63,7 +63,7 @@ curl -v ${CODER_ACCESS_URL}/healthz
63
63
64
64
The output of this command should aid further diagnosis.
65
65
66
- ### < a name = " EACS04 " >EACS04 : /healthz did not return 200 OK</ a >
66
+ ### EACS04: /healthz did not return 200 OK
67
67
68
68
** Problem:** Coder was able to execute a GET request to
69
69
` ${CODER_ACCESS_URL}/healthz ` , but the response code was not ` 200 OK ` as
@@ -84,14 +84,14 @@ should give you a good indication of the root cause.
84
84
Coder continuously executes a short database query to validate that it can reach
85
85
its configured database, and also measures the median latency over 5 attempts.
86
86
87
- ### < a name = " EDB01 " >EDB01 : Database Ping Failed</ a >
87
+ ### EDB01: Database Ping Failed
88
88
89
89
** Problem:** This error code is returned if any attempt to execute this database
90
90
query fails.
91
91
92
92
** Solution:** Investigate the health of the database.
93
93
94
- ### < a name = " EDB02 " >EDB02 : Database Latency High</ a >
94
+ ### EDB02: Database Latency High
95
95
96
96
** Problem:** This code is returned if the median latency is higher than the
97
97
[ configured threshold] ( ../cli/server.md#--health-check-threshold-database ) . This
@@ -120,7 +120,7 @@ traffic between Coder and workspace agents. Coder periodically queries the
120
120
health of its configured DERP servers and may return one or more of the
121
121
following:
122
122
123
- ### < a name = " EDERP01 " >EDERP01 : DERP Node Uses Websocket</ a >
123
+ ### EDERP01: DERP Node Uses Websocket
124
124
125
125
** Problem:** When Coder attempts to establish a connection to one or more DERP
126
126
servers, it sends a specific ` Upgrade: derp ` HTTP header. Some load balancers
@@ -137,7 +137,7 @@ still be able to reach their workspaces, connection performance may be degraded.
137
137
** Solution:** ensure that any configured reverse proxy does not strip the
138
138
` Upgrade: derp ` header.
139
139
140
- ### < a name = " EDERP02 " >EDERP02 : One or more DERP nodes are unhealthy</ a >
140
+ ### EDERP02: One or more DERP nodes are unhealthy
141
141
142
142
** Problem:** This is shown if Coder is unable to reach one or more configured
143
143
DERP servers. Clients will fall back to use the remaining DERP servers, but
@@ -170,7 +170,7 @@ functionality, Coder will periodically attempt to establish a WebSocket
170
170
connection with itself using the configured [ Access URL] ( #access-url ) , send a
171
171
message over the connection, and attempt to read back that same message.
172
172
173
- ### < a name = " EWS01 " >EWS01 : Failed to establish a WebSocket connection</ a >
173
+ ### EWS01: Failed to establish a WebSocket connection
174
174
175
175
** Problem:** Coder was unable to establish a WebSocket connection over its own
176
176
Access URL.
@@ -187,7 +187,7 @@ Access URL.
187
187
2 . Ensure that any reverse proxy that is sitting in front of Coder's configured
188
188
access URL is not stripping the HTTP header ` Upgrade: websocket ` .
189
189
190
- ### < a name = " EWS02 " >EWS02 : Failed to echo a WebSocket message</ a >
190
+ ### EWS02: Failed to echo a WebSocket message
191
191
192
192
** Problem:** Coder was able to establish a WebSocket connection, but was unable
193
193
to write a message.
@@ -206,23 +206,23 @@ to write a message.
206
206
If you have configured [ Workspace Proxies] ( ../admin/workspace-proxies.md ) , Coder
207
207
will periodically query their availability and show their status here.
208
208
209
- ### < a name = " EWP01 " >EWP01 : Error Updating Workspace Proxy Health</ a >
209
+ ### EWP01: Error Updating Workspace Proxy Health
210
210
211
211
** Problem:** Coder was unable to query the connected workspace proxies for their
212
212
health status.
213
213
214
214
** Solution:** This may be a transient issue. If it persists, it could signify a
215
215
connectivity issue.
216
216
217
- ### < a name = " EWP02 " >EWP02 : Error Fetching Workspace Proxies</ a >
217
+ ### EWP02: Error Fetching Workspace Proxies
218
218
219
219
** Problem:** Coder was unable to fetch the stored workspace proxy health data
220
220
from the database.
221
221
222
222
** Solution:** This may be a transient issue. If it persists, it could signify an
223
223
issue with Coder's configured database.
224
224
225
- ### < a name = " EWP03 " >EWP03 : Workspace Proxy Version Mismatch</ a >
225
+ ### EWP03: Workspace Proxy Version Mismatch
226
226
227
227
** Problem:** One or more workspace proxies are more than one major or minor
228
228
version out of date with the main deployment. It is important that workspace
@@ -232,14 +232,14 @@ of API incompatibility.
232
232
** Solution:** Update the workspace proxy to match the currently running version
233
233
of Coder.
234
234
235
- ### < a name = " EWP04 " >EWP04 : One or more Workspace Proxies Unhealthy</ a >
235
+ ### EWP04: One or more Workspace Proxies Unhealthy
236
236
237
237
** Problem:** One or more workspace proxies are not reachable.
238
238
239
239
** Solution:** Ensure that Coder can establish a connection to the configured
240
240
workspace proxies on port 443.
241
241
242
- ## < a name = " EUNKNOWN " > Unknown Error</ a >
242
+ ## Unknown Error
243
243
244
244
** Problem:** This error is shown when an unexpected error occurred evaluating
245
245
deployment health. It may resolve on its own.
0 commit comments