If your QuickBox install suddenly stopped verifying, or QBXWatcher pinged you in Discord to run /verify again, nothing is broken on your server. What changed is on our side, and it's on purpose. The old quickbox.io site is being retired, and QuickBox installs no longer check their license against its API. This is a short, direct guide to what changed, why you're seeing it, and the exact steps to move your license to v3.quickbox.io so you're verified for good.
What actually changed
License checks used to run against the legacy quickbox.io site, the platform that predates everything we've built on v3.quickbox.io. Verification now runs only against your v3.quickbox.io account. The old license endpoints your install used to hit are retired for verification.
We didn't do this to make your life harder. Keeping the old check alive kept accounts tethered to a platform we're sunsetting, so people put the move off indefinitely. Moving verification to v3.quickbox.io is the push that gets everyone onto the system we actually maintain.
Note
Your install keeps running. This is about license verification and your Verified role in Discord, not about your apps or your data. Nothing on your server is deleted or disabled.
Why you're seeing a verify failure or a /verify nudge
When your install or the bot tries to verify and your license isn't in the v3.quickbox.io system yet, there's nothing on the new side to match against, and the old side is gone. That's the failure you're seeing, usually a plain HTTP 404: Not Found from an endpoint that no longer exists.
QBXWatcher runs a recheck every day. If it can't confirm your verification, it opens a 7-day grace window and asks you to run /verify again instead of pulling your role right away. That grace period is your time to migrate. Once your license is on v3.quickbox.io, /verify succeeds and the reminders stop.
Move your license to v3.quickbox.io
This takes a few minutes. You'll need your old quickbox.io login and your legacy API key.
1. Create your v3.quickbox.io account
Go to https://v3.quickbox.io/register and sign up with the email tied to your QuickBox purchase. If you already have an account, just log in.
2. Run the migration utility
Open the License Migration page at https://v3.quickbox.io/dashboard/migrate. It walks you through three steps:
- ●Enable & Prepare. In Settings -> Preferences, toggle on "Legacy License Migration." Then run
qb manage apion your server to read your legacy API key (and your instance IDs if you run more than one box). - ●Verify Ownership. Enter your old quickbox.io username and password plus that legacy API key, then click Verify License. This confirms the license is yours and shows your migration summary.
- ●Migrate & Update Servers. Approve the confirmation, copy your new v3 API key, then run these on every server:
qb manage api -o deactivate
qb manage api -k NEW_KEY
qb manage telemetry -o on
Tip
Not sure where your legacy API key is? Three ways to find it: run qb manage api on the server, check your account on the classic site at https://quickbox.io/my-account/api-keys/, or open System -> API Control in your dashboard.
That's it. Your license now lives on v3.quickbox.io, your servers point at the new key, and /verify in Discord will confirm you.
Full walkthrough in the docs: https://v3.quickbox.io/docs/v3-portal/migration-utility
Seeing "GLIBC_2.33 not found"? You're on Debian 11
If your install throws an error like GLIBC_2.33' not found, that isn't a license problem, it's your operating system. It means you're on Debian 11 (Bullseye), which has reached end of life and is off our supported channel. The binaries QuickBox ships are built for newer, supported releases, so they can't run against Debian 11's older system libraries.
The fix is to move to Debian 12 first, then update and migrate:
- Upgrade Debian 11 to Debian 12 with our step-by-step guide: Upgrading Debian 11 (Bullseye) to Debian 12 (Bookworm) Without Breaking Your Server.
- Run
qb update quickboxto pull the current release. - Then follow the migration steps above.
Warning
Don't skip the distro upgrade and try to force the install. Debian 11 is EOL, so staying on it means no security updates and software that keeps breaking as everything else moves forward. The upgrade guide is written to preserve your service configs and survive an SSH disconnect.
Where to get help
- ●Supported operating systems and fresh-install requirements: https://v3.quickbox.io/docs/getting-started
- ●The full migration walkthrough: https://v3.quickbox.io/docs/v3-portal/migration-utility
- ●Still stuck after migrating? Ask in Discord, and run
/verifyfirst so we can see your current status.
Moving to v3.quickbox.io is a one-time step, and it puts you on the platform we're actively building. Get it done inside your grace window and you're set.
On a much older PHP-based install? Come talk to us
If you're coming from a much older, PHP-based version of QuickBox and the update or migration isn't going smoothly, don't wrestle with it alone. These older installs sometimes need a hand to bring current, and that's exactly what we're here for. Hop into our Discord and the team will walk you through it, step by step.
