If grok.com just spins or returns a connection error, start with the basics: clear your browser cache, try a different browser, or switch from Wi-Fi to mobile data. Sometimes a stale DNS cache is the culprit — flush it with ipconfig /flushdns on Windows or sudo dscacheutil -flushcache on Mac.
Failed login attempts usually come down to a few things:
The interface freezes and the response just cuts off. This usually happens when the WebSocket connection drops. Reload the page — Grok often saves context, so you won't lose the whole conversation. If it keeps happening, disable browser extensions one by one; ad blockers sometimes interfere with streaming responses.
If your prompt hangs on 'sending' indefinitely, check your network stability first. High packet loss wrecks the real-time connection the service relies on. Run a quick ping test — if you're seeing above 150ms or dropped packets, the issue is on your network side. Switching to a wired connection usually fixes it.
Supported formats are JPEG, PNG, and a few others — uploading a HEIC photo straight from an iPhone will fail silently. Convert the file first. Also check file size; anything over the limit just gets rejected without a clear error message in some browser versions.
Long conversations can cause the frontend to bog down, especially on older hardware. The fix is straightforward: start a new chat. If sluggishness persists across sessions, try the mobile app instead of the web version — it handles memory more efficiently.