'Failed to Fetch' and Other Mystery Errors
What 'Failed to fetch', 'Network error', and other vague messages actually mean, and what to do about them.
You'll learn
- What the most common vague error messages actually mean
- A 30-second checklist to rule out problems on your end
- Where to check whether AwardLettr itself is having an outage
You clicked something and got a red toast that said 'Failed to fetch'. Or 'Network error'. Or the page just sat there spinning. Or you got 'Something went wrong' with no other detail. None of those messages tell you what is actually broken, which is infuriating when you just want to save your work and move on.
Almost all of these errors share one cause: your browser tried to talk to our servers and the round trip failed. The browser does not get told why. It could be a momentary blip on your wifi, a VPN that just dropped, a corporate firewall having a moment, a request that timed out, or (rarely) an outage on our side. They all surface as the same handful of vague messages because at the network layer, there is nothing more specific to report.
The good news is the fix is almost always boring: refresh the page. The 30-second checklist below rules out the common causes on your end in well under a minute. If it keeps happening after you have walked through it, that is when to grab a screenshot and message support so we can check whether it is us.
'Failed to fetch' is the worst error message in software because it tells you nothing. Here is the translation: your browser tried to talk to our servers and could not reach them. That is it. There is no detail because at the network level, there is no detail to give.
What you see
- Red error toast saying "Failed to fetch"
- Page that never loads, just spins
- "Network error" with no other context
- "Something went wrong" with a generic icon
What it usually means
- Temporary connection issue, refresh the page
- Your internet hiccuped or your VPN dropped
- Same — a request to our server timed out
- Our server returned an unexpected response, try again
30-second checklist
- Refresh the page (Cmd+R on Mac, Ctrl+R on Windows).
- Check another website like google.com — if that fails too, your internet is the problem.
- If you are on a VPN or corporate network, try disconnecting briefly to test.
- Open the AwardLettr status page (status.awardlettr.com) if/when available, to see whether we are reporting an incident.
- If the error keeps happening, message support with a screenshot.
When AwardLettr itself is down
Other vague errors and what they mean
| What you see | What it means | What to do |
|---|---|---|
| 'Loading...' forever | The page made a request that never returned an answer | Wait 30 seconds, then refresh. If it happens again, message support with the page URL. |
| 'Something went wrong' | Our server returned an error but the page handled it generically | Refresh. If it persists, open the browser dev tools (F12), copy the Console error, and send it to support. |
| Page is blank / white | A JavaScript error broke the page before it could render | Hard refresh (Cmd+Shift+R or Ctrl+Shift+R) to bypass cache. If still blank, try an Incognito/Private window. |
| 'You are offline' | Your browser thinks it has no internet connection | Check your wifi or ethernet. Try loading a different site to confirm. |
When you message support about a mystery error, include a screenshot of the full browser window (with the error visible), the page URL, and what you were doing when it happened. That triple makes it 10x faster to diagnose.
Related Articles
Common Error Messages, Decoded
A reference table for the error messages you will actually see in AwardLettr and exactly what to do about each one.
Contact Support
How to reach AwardLettr support, what info to include, and which channel is right for which problem.
Email Isn't Sending: Diagnostic Walkthrough
Step through the most common reasons an email failed to send from AwardLettr and how to fix each one.