Common issues when connecting Android devices or sending SMS through your workspace gateway.

App shows Offline

Check	Action
API URL	Must match Status tab exactly, including https:// and path
Private Token	Re-copy from portal; no extra spaces
Phone network	Open API URL in mobile browser — should not timeout
Cloud Server switch	Enabled on app Home tab
Gateway health	Portal Status cards should show ready; contact support if red

Try: open Connect with QR again from the portal and rescan in Settings → Cloud server, or disable Cloud Server → re-enter URL/token → enable → start again.

Device not in portal list

1. Confirm app status Online for at least one minute.
2. Refresh Devices tab.
3. Regenerate login code from Status if app requested pairing.
4. Remove old device entries if you replaced the phone.

Messages stuck Pending

• Verify device still Online on Devices tab.
• Check SIM balance and cellular signal on the phone.
• Keep app running in background; disable aggressive battery savers.
• Open message detail for error hint; check Manager → Logs in portal.
• Private gateway push: the server wakes the phone via https://api.sms-gate.app/upstream/v1/push (token + event only; no message body). From the host running PM2, check egress: curl -m 15 -sI https://api.sms-gate.app/. Push send timeout defaults to 15 seconds (FCM__TIMEOUT_SECONDS). Logs showing context deadline exceeded on that URL usually mean slow/blocked outbound HTTPS or a too-short timeout on an old binary — rebuild sms-gateway, ensure the tenant .env has FCM__TIMEOUT_SECONDS=15, then reload PM2 with --update-env.

Messages Failed

Cause	Fix
Invalid recipient number	Use E.164 format (+country code…)
Device offline	Bring app Online before sending
No SMS permission	Re-grant permissions in Android settings
Carrier block	Test with another number; check regional SMS rules

Webhooks not firing

• URL must be public HTTPS.
• Confirm webhook registered (portal dialog or list webhooks API).
• Return 2xx quickly from your endpoint.
• Check gateway logs for delivery errors to your URL.

Health check failures

If monitoring reports not ready:

1. Open portal SMS Gateway → Status.
2. Review health card messages.
3. Contact support with workspace subdomain and timestamp if service down persists.

Subscription or access issues

• Service not enabled — Enable SMS on plan or request add-on from portal upsell.
• Subscription expired — Renew from Billing.

Still stuck?

Use Technical support in the portal sidebar (WhatsApp link) or contact via aysali.com. Include:

• Workspace subdomain
• Device model and app version
• Screenshot of app connection status
• Approximate time of failed test message

Related