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
{{ message }}
Repository navigation
Commit cf0f3d0
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(gateway)!: replace the file-configured proxy certificate with Admin.ImportCert
`[core.proxy] cert_chain`/`cert_key` installed a certificate that lived in
no KV key, so any cert store reload built from KV dropped it, taking
`<id>.<base_domain>` routing down with it. Production deployments do not set
it: certificates are issued by the distributed certbot and kept in KV.
Remove it, and `base_domain`, which only named the domain for it. A
certificate issued elsewhere is now installed with `Admin.ImportCert`, which
stores it in KV like an issued one, so it replicates and survives reloads.
The gateway does not renew it.
The proxy data-path suite imports its test certificate through the RPC; the
cluster suite and dev-stack.sh no longer configure one.
Copy file name to clipboardExpand all lines: docs/dstack-gateway.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,14 +23,11 @@ records that pin issuance to its own ACME account.
23
23
24
24
Focus on these fields in the `core.proxy` section:
25
25
26
-
-`base_domain`: the wildcard domain for the proxy
27
26
-`listen_addr` & `listen_port`: listen on `0.0.0.0` and preferably `443` in production. If using another port, specify it in the URL (see [URL Format](#url-format))
28
27
29
28
For example, if your base domain is `gateway.example.com`, app ID is `<app_id>`, listening on `80`, and dstack-gateway is on port 7777, the URL would be `https://<app_id>-80.gateway.example.com:7777`
30
29
31
-
Leave `cert_chain` and `cert_key` unset. They load a certificate you already
32
-
have from disk at startup, for the case where something else issues it; the
33
-
gateway's own issuance does not use them and does not write them.
30
+
The base domain is not set here: it is the ZT domain you add in Step 3.
0 commit comments