Gitead/DentalManagement09
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: LAN HTTPS Step 4 — paste the existing Cloudflare token; creating a new one is the fallback

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Gitead
2026-10-06 22:33:21 -04:00
co-authored by Claude Opus 5.5
parent d3a658462f
commit d67e68c957
1 changed files with 20 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+20 -25
View File
@@ -812,30 +812,16 @@ sudo apt update
sudo apt install -y certbot python3-certbot-dns-cloudflare sudo apt install -y certbot python3-certbot-dns-cloudflare
``` ```
### Step 4 — Create a scoped Cloudflare API token ### Step 4 — Add the Cloudflare API token
**4a. Create the token (in a browser):** Use the existing Cloudflare API token (the same one works for every office PC). Open the credentials file:
1. Go to `dash.cloudflare.com` → profile icon (top right) → **My Profile** → **API Tokens** → **Create Token**
2. Use the **Edit zone DNS** template
3. Under **Zone Resources**, choose **Specific zone** → `mydentalofficemanagement.com`
4. Click **Continue to summary** → **Create Token**, then copy the token. It's only shown once.
**4b. Check the token works** (replace `YOUR_TOKEN`):
```sh
curl -s -H "Authorization: Bearer YOUR_TOKEN" https://api.cloudflare.com/client/v4/user/tokens/verify
# should include: "status":"active"
```
**4c. Save it in a root-only credentials file:**
```sh ```sh
sudo mkdir -p /etc/letsencrypt sudo mkdir -p /etc/letsencrypt
sudo nano /etc/letsencrypt/cloudflare.ini sudo nano /etc/letsencrypt/cloudflare.ini
``` ```
Make the file exactly this one line, with your token pasted after `= ` (paste in the terminal with `Ctrl+Shift+V`; clear old lines with `Ctrl+K`): Paste this one line, with the token after `= ` (paste in the terminal with `Ctrl+Shift+V`):
```ini ```ini
dns_cloudflare_api_token = <paste token here> dns_cloudflare_api_token = <paste token here>
@@ -848,15 +834,24 @@ sudo chmod 600 /etc/letsencrypt/cloudflare.ini
``` ```
> **If certbot fails with `Error determining zone_id: 6003 Invalid request headers`,** the token in > **If certbot fails with `Error determining zone_id: 6003 Invalid request headers`,** the token in
> this file is malformed: the `<paste token here>` placeholder was left in, there are extra > this file is wrong: the `<paste token here>` placeholder was left in, there are extra characters
> characters or quotes, or the token ID / Global API Key was copied instead of the token itself. > or quotes, or the token ID / Global API Key was copied instead of the token itself. Check it with
> Check it with `sudo cat /etc/letsencrypt/cloudflare.ini`, re-test with 4b, fix the file, and run > `sudo cat /etc/letsencrypt/cloudflare.ini`, fix the file, and run Step 5 again. To test a token
> Step 5 again. (The yellow `PendingDeprecationWarning` box certbot prints about the `cloudflare` > on its own:
> Python package is harmless.) > ```sh
> curl -s -H "Authorization: Bearer YOUR_TOKEN" https://api.cloudflare.com/client/v4/user/tokens/verify
> # should include: "status":"active"
> ```
> (The yellow `PendingDeprecationWarning` box certbot prints about the `cloudflare` Python package
> is harmless.)
> The same token can be reused across offices (Cloudflare tokens are scoped to the whole zone, #### Only if you don't have a token yet (or it was revoked)
> not a single subdomain) — but issuing one token per server makes it easy to revoke just one if
> a machine is ever decommissioned. 1. Go to `dash.cloudflare.com` → profile icon (top right) → **My Profile** → **API Tokens** → **Create Token**
2. Use the **Edit zone DNS** template
3. Under **Zone Resources**, choose **Specific zone** → `mydentalofficemanagement.com`
4. Click **Continue to summary** → **Create Token**, then copy the token. It's only shown once, so
save it in a password manager for the next PC.
### Step 5 — Issue the certificate ### Step 5 — Issue the certificate