Domains
?
Managed websites and challenge-ready validation sessions.
sslbag
Separate frontend workspace
Backend session
No active Laravel session detected.
user app shell
Separate frontend view for customer domains, certificates, downloads, and renewal actions. It already reads the public runtime contract and will consume authenticated dashboard data as the frontend/backend split is finalized.
Domains
?
Managed websites and challenge-ready validation sessions.
Active certificates
?
Current versions stored and downloadable for the signed-in user.
Renewal due
?
Issued versions that need a fresh DNS or HTTP validation flow.
Expiring soon
?
Certificates that are inside the current reminder windows.
No authenticated dashboard data yet
Backend request failed with status 404. The split frontend will use backend session or Sanctum auth next.
Protected backend data requires a Laravel session
Open the live backend login first, then return to the separated frontend. The split app already knows how to consume the protected API contract once those cookies are shared in deployment.
Certificate activity will appear here
This split frontend is ready for the authenticated certificate feed. Once session bridging is in place, the list will render from the backend contract.