Overall
TrustedQueue is running with warnings
Environment: production
The service is available, but one or more non-blocking checks needs attention from the site owner.
Overall
TrustedQueue is running with warnings
Environment: production
Passing
20
Checks currently passing.
Warnings
4
Non-blocking checks needing attention.
Failures
0
Blocking checks affecting readiness.
Public-safe availability for the main TrustedQueue flows. These summaries do not expose private reports, source payloads, credentials, or admin-only diagnostics.
Steam sign-in readiness checks are passing.
Sign inSteam verification refresh should be available.
Open verificationQueue, lobby, invite, and preflight actions are available.
Find teammatesPrivate reports, appeals, and support workflows should be available.
Open supportPublic pages and production URL checks are passing.
Open homeWarnings usually mean a non-blocking deployment, source, queue, or diagnostic check needs owner review. Sign-in may still work, but some verification or queue features can look limited.
Start with the page tied to the issue, then use private support only when the guided path does not clear it. Keep reports and appeals in their protected workflows.
You signed in, but a protected page still asks for Steam login or redirects unexpectedly.
TrustedQueue never asks for Steam passwords or personal Steam API keys.
Your profile shows limited verification, missing stats, or no FACEIT skill context.
FACEIT is optional. Linking it can strengthen context, but not having FACEIT is allowed.
Discovery is empty or filters return very few players.
Small early pools are normal; discovery only shows real eligible accounts.
A lobby exists, but invite or contact details are still hidden.
Contact reveal depends on fresh source and platform checks for every lobby member.
Something happened in a TrustedQueue lobby and you want it reviewed.
Reports, reporter identity, and evidence stay private and are not public profile content.
Your account cannot join queue or lobby flows because of a restriction.
Appeals are reviewed privately and moderation evidence remains protected.
This page uses public-safe health details only. It does not expose API keys, database URLs, session data, private reports, moderation evidence, or admin audit metadata.
Health route is responding.
Queue, lobby, invite, and preflight actions are available.
Database connection succeeded.
Latest expected Prisma migration is applied: 20260630003000_add_account_notification_preferences.
Required runtime database columns are present.
No recent critical/error operational logs recorded.
DATABASE_URL is configured.
DIRECT_URL is configured for Prisma migration deploys.
Session signing secret is present.
NEXT_PUBLIC_SITE_URL is configured.
Steam OpenID realm and callback URL are configured.
Steam API key is configured server-side.
1 admin SteamID64 value configured.
Set CRON_SECRET before enabling scheduled maintenance jobs.
Operational alerts are disabled. Enable them before relying on production monitoring.
Product event alerts are disabled. Enable them before relying on owner/admin notifications.
Diagnostic/source-check retention: operational errors 90d, integration logs 180d, verification checks 180d.
Record backup provider, dashboard URL, and latest restore drill before launch. Missing: DATABASE_BACKUP_PROVIDER, DATABASE_BACKUP_DASHBOARD_URL, DATABASE_BACKUP_LAST_RESTORE_TEST_AT.
Development-only login is disabled for production.
FACEIT API key is configured server-side.
Leetify remains disabled unless a permitted integration is configured.
Public simulator launch and equipped-loadout reads are available. Signed-in API handoff is optional unless a provider-issued API key becomes available.
CS2 server address is configured for the Servers page connect flow.
Steam OpenID URLs match the production public site and callback route.