2
2
3
3
Frequently asked questions on Coder OSS and Enterprise deployments. These FAQs
4
4
come from our community and enterprise customers, feel free to
5
- [ contribute to this page] ( https://github.com/coder/coder/edit/main/docs/faqs.md ) .
5
+ [ contribute to this page] ( https://github.com/coder/coder/edit/main/docs/tutorials/ faqs.md ) .
6
6
7
7
For other community resources, see our
8
8
[ Github discussions] ( https://github.com/coder/coder/discussions ) , or join our
@@ -20,8 +20,7 @@ In the UI, click the Deployment tab -> Licenses and upload the `jwt` license
20
20
file.
21
21
22
22
> To add the license with the CLI, first
23
- > [ install the Coder CLI] ( ./install/index.md#install-script ) and server to the
24
- > latest release.
23
+ > [ install the Coder CLI] ( ../install/cli.md ) and server to the latest release.
25
24
26
25
If the license is a text string:
27
26
@@ -41,8 +40,8 @@ The primary developer use case is a local IDE connecting over SSH to a Coder
41
40
workspace.
42
41
43
42
Coder's networking stack has intelligence to attempt a peer-to-peer or
44
- [ Direct connection] ( https://coder.com/docs /networking#direct-connections)
45
- between the local IDE and the workspace. However, this requires some additional
43
+ [ Direct connection] ( ../admin /networking/README.md #direct-connections) between
44
+ the local IDE and the workspace. However, this requires some additional
46
45
protocols like UDP and being able to reach a STUN server to echo the IP
47
46
addresses of the local IDE machine and workspace, for sharing using a Wireguard
48
47
Coordination Server. By default, Coder assumes Internet and attempts to reach
@@ -56,11 +55,11 @@ to establish these direct connections.
56
55
Setting the following flags as shown disables this logic to simplify
57
56
troubleshooting.
58
57
59
- | Flag | Value | Meaning |
60
- | -------------------------------------------------------------------------------------------------------------- | ----------- | ------------------------------------- |
61
- | [ ` CODER_BLOCK_DIRECT ` ] ( https://coder.com/docs /reference/cli/server#--block-direct-connections) | ` true ` | Blocks direct connections |
62
- | [ ` CODER_DERP_SERVER_STUN_ADDRESSES ` ] ( https://coder.com/docs /reference/cli/server#--derp-server-stun-addresses) | ` "disable" ` | Disables STUN |
63
- | [ ` CODER_DERP_FORCE_WEBSOCKETS ` ] ( https://coder.com/docs /reference/cli/server#--derp-force-websockets) | ` true ` | Forces websockets over Tailscale DERP |
58
+ | Flag | Value | Meaning |
59
+ | ------------------------------------------------------------------------------------------ | ----------- | ------------------------------------- |
60
+ | [ ` CODER_BLOCK_DIRECT ` ] ( .. /reference/cli/server#--block-direct-connections) | ` true ` | Blocks direct connections |
61
+ | [ ` CODER_DERP_SERVER_STUN_ADDRESSES ` ] ( .. /reference/cli/server#--derp-server-stun-addresses) | ` "disable" ` | Disables STUN |
62
+ | [ ` CODER_DERP_FORCE_WEBSOCKETS ` ] ( .. /reference/cli/server#--derp-force-websockets) | ` true ` | Forces websockets over Tailscale DERP |
64
63
65
64
### How do I configure NGINX as the reverse proxy in front of Coder?
66
65
@@ -124,9 +123,9 @@ resource "coder_app" "code-server" {
124
123
An important concept to understand is that Coder creates workspaces which have
125
124
an agent that must be able to reach the `coder server`.
126
125
127
- If the [`CODER_ACCESS_URL`](https://coder.com/docs/ admin/configure#access-url)
128
- is not accessible from a workspace, the workspace may build, but the agent
129
- cannot reach Coder, and thus the missing icons. e.g., Terminal, IDEs, Apps.
126
+ If the [`CODER_ACCESS_URL`](../ admin/configure.md #access-url) is not accessible
127
+ from a workspace, the workspace may build, but the agent cannot reach Coder, and
128
+ thus the missing icons. e.g., Terminal, IDEs, Apps.
130
129
131
130
> By default, `coder server` automatically creates an Internet-accessible
132
131
> reverse proxy so that workspaces you create can reach the server.
@@ -154,9 +153,9 @@ of these values can lead to existing workspaces failing to start. This issue
154
153
occurs because the Terraform state will not be in sync with the new template.
155
154
156
155
However, a lesser-known CLI sub-command,
157
- [`coder update`](https://coder.com/docs/ reference/cli/update), can resolve this
158
- issue. This command re-prompts users to re-enter the input variables,
159
- potentially saving the workspace from a failed status.
156
+ [`coder update`](../ reference/cli/update), can resolve this issue. This command
157
+ re-prompts users to re-enter the input variables, potentially saving the
158
+ workspace from a failed status.
160
159
161
160
` ` ` sh
162
161
coder update --always-prompt <workspace name>
0 commit comments