Verifying Your License

Verification proves that the Discord account you are using belongs to a QuickBox Pro licence holder. Once verified you get the 🌟Verified role, which unlocks the commands that reach out to your own server.

There are two ways to verify. Use /verify. It is a short conversation in your DMs, it needs nothing from your server, and completing it links your Discord account to your QuickBox Pro account — which is what makes everything you do afterwards easier. The second route exists for licences that predate the portal, or if you would simply rather verify against the installation itself.

Option 1 — the conversational flow (recommended)

Run this in any channel of the QuickBox Discord server:


/verify

QBXWatcher opens a DM with you and asks for the email address or username you use at v3.quickbox.io. It then emails an eight-digit code to the address on that account — shown as 1234-5678 for readability — and you paste the code back into the DM. The code is valid for 10 minutes and you get five attempts.

1. Run /verify

The bot opens a DM and replies in the channel telling you to check it

2. Give your identity

Reply with the email or username you use at v3.quickbox.io

3. Paste the emailed code

Eight digits, valid for 10 minutes, five attempts

4. Role granted and account linked

The 🌟Verified role is added and your Discord is linked to your QuickBox Pro account

Finishing /verify also closes out the onboarding quest for you. It is marked complete quietly — no extra DM, nothing further to run — so a licence holder who verifies this way is done in one step rather than two.

No v3.quickbox.io account?

This flow resolves against a v3.quickbox.io account, so you need one. If your licence is still on the older quickbox.io platform, the better fix is to bring it across with the Migration Utility — registering with Sign in with Discord creates the account and links your Discord identity in one step. If you would rather not, type woocommerce when the bot asks for your email and it will close the conversation and point you at /verify-start, which is described below and still works.

Useful things to know during the conversation:

Type this	What happens
an email or username	Starts the emailed-code challenge against your v3.quickbox.io account
woocommerce	Switches to the API-key flow for licences bought outside the portal
resend	Sends a fresh code if the first email did not arrive
/cancel	Stops the conversation. You can start again with /verify at any time

Check your spam folder

The verification email is transactional and occasionally lands in spam. If it is not in your inbox within a minute, look there before typing resend. You get five attempts at the code; after that the challenge is retired and you start over with /verify.

If the bot cannot DM you

Discord blocks DMs from server members if the corresponding privacy setting is off, and verification cannot start. Fix it in three steps:

Tap the server name at the top of the channel list to open Server Settings.
Choose Privacy Settings.
Turn Allow direct messages from server members on.

Then run /verify again. That setting applies to the QuickBox server only — your other servers are unaffected.

Option 2 — verify by install type

If you would rather verify against your own installation, use:


/verify-start

QBXWatcher asks whether your QuickBox Pro install is remote or local, then opens the matching form.

Remote server

For a box reachable at a public URL.

Field	What to enter
QuickBox Server URL	The URL your dashboard is served on, for example `https://box.example.com`
Read Permissions Key	Found in your dashboard under System > API Control > QB Control API

Local server (home or LAN)

For an install that is not publicly reachable. Every value comes from the output of qb manage api on the server.

Field	What to enter
Local IP Address	The LAN address of the server, for example `192.168.1.100`
Instance ID	The instance identifier printed by `qb manage api`
Product ID	Only required for legacy keys — leave blank for keys that begin with `qbp_`
API Key	The key printed by `qb manage api`

Credentials are entered in a private form

Both forms are Discord modals — nothing you type is posted to a channel. Stored credentials are encrypted at rest.

Checking your status


/verify-status

The reply is private and shows your license state, verification type (local or remote), when you were last verified, the server URL on file, and the activation count on your licence. It also surfaces a grace period if one is active.

What you might see	What it means
🌟 Verified / ✅ Active	Everything is in order — verified commands are available
❌ Not Verified	You have not completed verification yet. Run `/verify`
⚠️ Grace Period Active	The bot could not reach your licence source recently. It tells you how many days remain before verification expires
🧃 Beta Squad: Yes	Your account is enrolled in the Beta Squad

A grace period is a warning, not a failure

A grace period usually means your server or the licence API was unreachable during a recheck — often a firewall change, an expired certificate, or a box that was offline. Bring the server back online and re-run /verify-status; the grace period clears on the next successful check.

After verification — what the link does for you

Completing /verify does two things: it grants the 🌟Verified role, and it writes the link between your Discord account and your QuickBox Pro account. That second half is quiet, but it is where the convenience comes from.

Once your Discord is linked, QBXWatcher can look your servers up by your Discord account rather than by an address you type in. In practice:

What changes	Why it helps
`/server add` offers your installs	Instead of a form asking for a URL and a read key, the bot lists the active installs already on your licence and you pick one. A single install becomes a confirm button
Every active licence counts	Subscription or lifetime — if the licence is active and the install is active, it shows up. There is no per-server setup step
Installs the bot cannot reach still work	A box on a home connection or behind NAT is not reachable from Discord. Those installs report telemetry to your account, and the bot reads that instead — so `/server status` and `/troubleshoot` still have something to show

Linking Discord does not skip the emailed code

Signing in to v3.quickbox.io with Discord links your identity there, and it is worth doing — but it is not a shortcut past verification. QBXWatcher always emails a fresh code and always waits for you to read it back. That step is what proves the person holding the Discord account also holds the mailbox on the licence, and it does not get bypassed.

Linking a server by hand is always available, and it is what you get if your Discord account is not linked on v3.quickbox.io — which is the usual case after /verify-start:


/server add

The success message offers a Link a Server button that starts the same flow. See Linking & Monitoring Servers for the full walkthrough.

If your Discord is already linked to another account

For security, QBXWatcher will not move a Discord link from one QuickBox Pro account to another. If your Discord account is already tied to a different account, verification stops and tells you so. Sign in to v3.quickbox.io as that account, unlink Discord under Dashboard → Settings → Connections, then run /verify again.

Best practices

Do

Verify with /verify — it needs nothing from your server and links your account so the server commands find your installs for you
Register on v3.quickbox.io with Sign in with Discord if you are creating the account now — it links your Discord identity in the same step
Use the read-only API key when a form asks for one
Enable server DMs before running /verify so the conversation can start
Re-run /verify-status after you move a server or change its URL
Type /cancel if you started verification by accident

Don't

Do not paste an API key or licence key into a public channel — every prompt is private
Do not share your verification email code with anyone, including staff
Do not ignore a grace-period warning; verification expires if it is never resolved
Do not create a second Discord account to re-verify — activations are counted against your licence

FAQ

Check your spam folder first. If it is not there, type 'resend' in the DM to trigger a fresh code. If it still does not arrive, the address on your v3.quickbox.io account may differ from the one you expect — sign in to the portal to confirm which address is on file.

The code is eight digits and appears in the body of the email, not the subject line. It is shown grouped as 1234-5678 to make it easier to read — the dash is only formatting, and typing it either way is fine. Copy it without surrounding spaces. You get five attempts; once they are used up the challenge is retired and you start over with /verify.

Not if you verify with /verify — finishing it marks the quest complete for you, quietly and with nothing more to run. If you verified by entering your install details with /verify-start instead, the quest may still be open; run /onboarding-progress to see where you stand.

No, and that is deliberate. QBXWatcher always emails a fresh code and waits for you to read it back, no matter what is already linked on your account. Signing in with Discord is still worth doing — it means the link is in place, which is what lets /server add offer your installs instead of asking you for a URL and a key.

A Discord account can only be tied to one QuickBox Pro account, and the bot will not move that link on its own. Sign in to v3.quickbox.io as the account that currently holds it, unlink Discord under Dashboard → Settings → Connections, then run /verify again.

Verification is rechecked periodically. If a recheck cannot reach your licence source you enter a grace period and the bot tells you how long you have to fix it. As long as your licence is active and reachable, nothing is required of you.

/verify is a DM conversation that identifies you by your v3.quickbox.io account and an emailed code, and it links your Discord account to that account as it completes. /verify-start identifies you by your installation instead, using either a public URL plus read key, or a LAN address plus the values from 'qb manage api'. Either grants the same Verified role, but only /verify creates the account link — so unless your Discord is already linked on v3.quickbox.io, after /verify-start you go on linking servers by hand.

Bring it across with the Migration Utility at /docs/v3-portal/migration-utility — that gives you a v3.quickbox.io account and the full /verify flow. If you would rather not migrate yet, type 'woocommerce' when the bot asks for your email and it will point you at /verify-start, where you supply your install details directly.

Run /verify-status. If you run /verify while you already hold the Verified role, the bot tells you so and points you at /server add instead.

No. Verifying links your account, not your machine. The bot only connects to your server after you link one with /server add, and only with the read key you supply. Separately, your install already reports its own health to your QuickBox Pro licence — the bot can read that, because it is your account's data, but reading it is not a connection to your box.

QBXWatcher Overview

What the bot does and how to talk to it

Linking & Monitoring Servers

Add a server after you verify

Command Reference

Every verification command and its options

Using the v3 Portal

Manage the account the bot verifies against

Migration Utility

Move a legacy quickbox.io licence to v3.quickbox.io

Join the Community

Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.

Dedicated Support

Feature Previews

Community Configs

Active Discussions

Join Discord Server