Applies to: Original Thuraya WE, using the OEM English/Arabic manual with no identified printed revision. The current OEM page lists WE as Legacy. This is not a current roaming, app-store availability or activation guarantee, and does not apply to IP Voyager or NEO products.
Work through these checks
Prove the local connection first
Join the installed WE SSID with its known Wi-Fi password; the label’s default SSID is WE-TCFxxxxx, but an administrator may have changed it. Open http://we.local or the installed management address (default 192.168.0.1). If Wi-Fi joins but the portal does not open, capture that local symptom before investigating satellite pointing. If the password is unknown, ask the owner; the manual warns that factory reset clears other settings too.
Read the actual network and submode
On the dashboard, distinguish Satellite Voice, Satellite Standard IP and Cellular. Only one network mode operates at once. Auto may switch networks when registration times out, so record the resulting network rather than the intended one. Satellite Voice allows calls/SMS; Standard IP disables them while providing data. Cellular has data/SMS but no native WE-app voice calls; third-party VoIP over data is a different service. A mode mismatch is not proof of failed hardware. Agree any switch with the administrator because active services are interrupted and a change may take up to three minutes.
Separate registration from the data session
For satellite, confirm current coverage and an unobstructed outdoor antenna view, then read SAPA and registration separately. If registration is slow, the manual directs you to Diagnostics > GNSS/GPS; preserve that result. After registration, keep the antenna in position. Internet additionally needs broadband data enabled and no administrator restriction. Ask the provider to verify the APN (the network gateway setting) and roaming entitlement rather than guessing values. If registered with data enabled but still offline, send support the exact state and requested diagnostic logs; System > Logs > Get Logs in the portal exports evidence, not a user repair or reset.
When to stop and get help
Stop for physical damage, unknown PIN/PUK or a critical system alert. Do not open the enclosure, guess credentials, reset factory settings, change emergency numbers or install unverified firmware. Network changes can interrupt active services; do not use emergency calls as a test.
What to tell support
Privately retain serial/IMEIs, firmware/app version, SIM/provider, location/time, SSID/local-portal result, actual mode, network-registration message, SAPA/GNSS observation, data/restriction state and exact alert text. Diagnostic logs are for support personnel, not public posting or end-user interpretation.
Original troubleshooting guidance based on the official sources below. Menu names can change. This is an independent guide, not a manufacturer service bulletin or a bench-tested repair.