[agentHits]

Summary

Adds a read-only Domains page at /dashboard/domains. It lists the domains of the active organization on each server the caller can read, with DNS status, certificate expiry, where the domain is used, and the last Traefik error.

Base: AgentHits-Dev. This PR does not depend on another open PR.

What the page shows

• One row per domain and server.
• Where the domain is used: the owning application or compose service, or the container name for a route that no panel service owns.
• DNS status from node:dns (A and AAAA, 5 s timeout, 10 minute cache), compared with the server address.
• Certificate expiry from Traefik's acme.json. Red under 14 days, yellow under 30 days.
• The last Traefik error for the domain, with its time, the original line, and a short explanation in Russian.
• A Traefik log block per server: the last 300 certificate and ACME lines from the last 7 days.

Access

The page uses the same gate as the Traefik File System page and settings.readTraefikFile.

• domainOverview.list and domainOverview.traefikLogs are protectedProcedure. Both call checkPermission({ traefikFiles: ["read"] }).
• The panel's own host needs owner or admin. A remote server needs access to that server. The two helpers moved from settings.ts to server/api/utils/traefik-files-access.ts, so both routers use one implementation.
• A server the caller cannot read is not contacted, and its domains are not listed.
• Certificate data needs hasProtectedResourceAccess: owner or admin, browser session, and an open super session. Without it, the page shows no certificate data and a notice. The other columns still load.
• The sidebar item and getServerSideProps check traefikFiles.read. Users without it are redirected to /.
• Both procedures are classified read in procedure-access.ts, like readTraefikFile.

Members with the Traefik files permission can open the page, not only owners and admins.

Private keys

acme.json contains keys. The server-side jq filter keeps only the domain names and the certificate field. Without jq, the whole file is read, and the panel drops the keys before anything else touches the data. Keys are never returned, logged, or put in an error message.

The feature never reads container environment variables. Route discovery reads container names and labels only.

Test plan

• apps/dokploy, domain-overview tests: bunx vitest run --config __test__/vitest.config.ts __test__/domain-overview. 7 files, 73 tests, all passing.
  • The router test has 13 access cases. It runs the real checkPermission and host checks against a fake member row.
  • The new access test has 3 cases: no contact with unreadable servers, no acme.json read without certificate access, and no key material in the response.
• Fault injection: I forced certificate access open, skipped the host check in the router, and removed the server filter in the service. Six tests failed. I restored the files.
• Full apps/dokploy suite on my local machine: 299 files, 3038 tests. 3028 passed, 4 failed, 6 skipped. The 4 failures are in __test__/deploy/application.real.test.ts, which runs real git clones and Docker builds. Docker is not running in my shell.
• CI, pr-check (test) (bun run test): 299 of 299 files passed. 3037 tests passed, 1 skipped (3038). That run includes application.real.test.ts, and it passed.
• CI, all other checks: audit and typecheck, pr-check (build), main-image-smoke, and the three service-image-builds jobs all passed.
• bunx tsc --noEmit passes in packages/server and in apps/dokploy.
• bunx biome check passes on the 23 changed files.

Not verified

• Not run against a live panel or live servers. The tests mock every command, DNS call, and database read.
• The 4 real-execution tests fail on my local machine, where Docker is not running. CI runs them on this branch and they pass.
• Container names from route labels are shown without the docker read permission that guards the Docker view.
• Panel domains and route owners are not filtered by a member's service access list. The overview page applies that filter; this page does not.
• ACME log lines are shown as they are, up to 2,000 characters each. A log line that printed a secret would show it to any user who can read the page.

🤖 Generated with Claude Code