Troubleshooting Common Linxi & Twilio Errors

Error 30034 — Message blocked by carrier

Cause: your A2P Campaign isn't approved yet, or the number isn't actually assigned to the Messaging Service the Campaign is registered under.

Fix: check your Campaign's status in Linxi Settings → Number Setup (or the Twilio console), and confirm the number shows up as a sender inside the correct Messaging Service. Verizon specifically tends to block traffic outright while a campaign is pending; AT&T and T-Mobile are usually more lenient during review, so this often shows up as "some carriers work, Verizon doesn't" before full approval.

Error 30908 — Privacy policy non-compliant

Cause: your privacy policy page is missing the exact language TCR checks for.

Fix: add this phrase verbatim to your privacy policy, then resubmit the campaign: "We do not share, sell, or provide your mobile phone number or messaging consent data to third parties or affiliates for marketing or promotional purposes." See Privacy Policy Guide for the full requirements.

Error 30909 — CTA/opt-in flow incomplete

Cause: your opt-in flow description is too vague — it doesn't specifically describe how consent is actually collected.

Fix: describe every opt-in method you use, quote the exact consent language shown to the person opting in, and link to your privacy policy directly in the description. See Opt-In Requirements.

Error 30882 — Terms & Conditions issues

Cause: your Terms & Conditions page is missing SMS-specific disclosures.

Fix: add STOP/HELP instructions, message frequency, and a data-rates disclosure to the T&C page itself, not just the privacy policy.

Inbound messages not appearing in Linxi

• Confirm the webhook URL is exactly https://linxi.app/webhook/inbound
• Confirm the number's routing shows as Active, not Inactive, in the Twilio console
• Confirm the number is actually assigned to the Messaging Service that has the webhook configured

See Webhook Configuration for the full setup.

"Credentials verified" in Linxi Settings, but the SMS test fails

• The number may not be assigned to a Messaging Service yet
• The Messaging Service may not have an A2P Campaign attached
• The Campaign may still be pending, or was rejected and needs resubmission

Messages show as "Queued," never "Delivered"

Normal and expected for Verizon while your Campaign is still under review. For other carriers, a message stuck in Queued for more than a few minutes usually means it's being filtered — check your Campaign's approval status.

502 Bad Gateway on Linxi

Cause: the Node.js process crashed, usually during a startup database migration error or a missing environment variable.

Fix (server admin): pm2 logs linxi --lines 30 to see the actual crash reason.

Square payment SDK not loading on checkout

Refresh the page and try again — the Square SDK loads asynchronously and can occasionally lose a race on a slow connection. Check the browser console for a blocked network request, and disable ad blockers, which sometimes flag third-party payment SDK scripts.

Can't find the Auth Token in the new console

Cause: the redesigned 1console.twilio.com moved account credentials off the main dashboard entirely — there's no longer a credentials widget on the landing page.

Fix: go to Settings → Account settings → API keys & auth tokens, then the Auth tokens tab. The Auth Token is hidden behind an eye icon next to "Primary auth token" — click it to reveal, then copy. See Create Twilio Account for the full walkthrough.

Messaging shows as "disabled" after setup

Cause: usually one of the four A2P prerequisites isn't actually complete yet — Compliance Profile, Brand, and Campaign all need to be approved, and the number needs to be attached to the Messaging Service that Campaign is registered under. Missing any one of these four leaves messaging effectively disabled even though the number itself looks active.

Fix: check each of the four independently rather than assuming approval of one implies the others — see the checklist in A2P Brand Registration.

Account SID isn't labeled clearly in 1console

Cause: the redesigned console shows the Account SID's value without a prominent "Account SID" label on the same page in every view, which trips people up if they're used to the old console's dashboard widget.

Fix: on the Settings → Account settings → API keys & auth tokens → Auth tokens tab, look for the 34-character string starting with AC — that's your Account SID, shown near the top of the page even without a bold label next to it.