From 75538126f22b2edbec53ce35e6d374b7215be6ff Mon Sep 17 00:00:00 2001 From: Gitead Date: Fri, 31 Jul 2026 10:11:36 -0400 Subject: [PATCH] docs: note server_names_hash_bucket_size fix for long local- hostnames Community Dentists of Lowell hit this during LAN HTTPS setup; documenting it in Step 6 saves the next office from rediscovering it. --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 7785cc23..898aa5ab 100644 --- a/README.md +++ b/README.md @@ -760,6 +760,16 @@ sudo cp nginx.conf /etc/nginx/sites-available/dental-app sudo nginx -t && sudo systemctl reload nginx ``` +> **If `nginx -t` fails with `could not build server_names_hash, you should increase +> server_names_hash_bucket_size: 64`:** the `local-.mydentalofficemanagement.com` +> hostname is too long for nginx's default hash bucket size. Fix it in the main config (not this +> repo's `nginx.conf`) — `/etc/nginx/nginx.conf` already has a commented-out line for this inside +> the `http { }` block: +> ```sh +> sudo sed -i 's/# server_names_hash_bucket_size 64;/server_names_hash_bucket_size 128;/' /etc/nginx/nginx.conf +> sudo nginx -t && sudo systemctl reload nginx +> ``` + ### Step 7 — Allow the new hostname in Vite and backend CORS - `apps/Frontend/vite.config.ts` → add the hostname to `server.allowedHosts`