If an AliasFleet page shows "Failed to load" with a Try Again button, or a section renders blank instead of your data, the page sent a request that did not complete. Your data is safe. Here is how to get the page back, starting with the one-click retry and ending with a support ticket if nothing else works.
Before you start#
These steps apply to the AliasFleet web dashboard in a modern browser (Chrome, Edge, Firefox, or Safari from the last two years). You need to be signed in. No special plan tier is required.
Start by looking at the exact wording of the error. Different messages point at different causes:
| Error text you see | Likely cause | Start with |
|---|---|---|
| "Failed to load" with a Try Again button | A single data request failed mid-load | Click Try Again |
| "Too many requests" or the page briefly works then fails again | The rate limit paused responses | See Too Many Requests |
| Section shows a spinner that never stops, or a blank panel | Stale cached data or a failed section fetch | Hard refresh the page |
| "No items found" when data should exist | A filter is hiding results, or one section failed | Clear filters, then hard refresh |
| Plain error page with a Cloudflare reference code | A server-side failure triggered our failover page | Wait 1-2 minutes, then retry |
How do I fix a "Failed to load" error?#
Click Try Again. Nearly every error screen in the dashboard has one. It reruns just the failed request without reloading the whole page, so your filters and open tabs stay put. In most cases the second attempt goes through.
If there is no retry button, or retry fails twice:
- Hard refresh the page. Hold Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac). This skips the browser cache and pulls a completely fresh copy of the page.
- Open the failing section on its own. If the rest of the dashboard works but one area fails (billing, activity logs, sent emails), open that page in a new tab to rule out a problem with the original tab.
- Wait one to two minutes, then try again. Short server hiccups usually clear by themselves. Do not keep hitting refresh every few seconds; rapid retries can trigger the rate limit.
How do I fix a section that loads blank or spins forever?#
That is almost always a stale browser cache fighting a fresh load. A hard refresh sorts it out.
- Hard refresh the page with Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac).
- Reset the filters. If a table or list shows "No items found" when you know the data is there, set filters, the search box, and the date range back to their defaults. A leftover filter can survive a failed load and hide everything.
- Sign out and back in. If the section still spins after a hard refresh, your session token may have expired without telling you. Sign out, sign back in, and reload the page. (If signing in itself fails, see Can't Log In.)
- Try another browser. If the same page keeps failing in one browser but works in another, the first browser's cache or an extension is the cause. Clear that browser's cache for aliasfleet.com, or switch its extensions off temporarily and retry.
What does a plain error page mean?#
It means the request never reached the dashboard code. If the whole site shows a plain error page with a Cloudflare reference code, our server returned an error and the failover page stepped in. Your data is unaffected; the web layer failed before the app could even render.
- Wait one to two minutes. These episodes are short, so give the server a moment to recover.
- Reload the page once. Do not open dozens of tabs; one reload is enough to confirm.
- Check whether other sites load. If nothing on the internet loads, the problem is your connection, not AliasFleet.
- Open a support ticket if the error page persists for several minutes, and include the Cloudflare reference code from the page. That code is the fastest way for us to find the failure in our logs.
How do I know the page is actually working again?#
Check first, then trust the data. After any recovery step:
- Reload the page normally (plain F5 or the browser's reload button).
- Confirm the numbers look right. Open a list you know well, such as your aliases, and check that the counts and entries match what you expect.
- Retry the action you were doing. If you were creating an alias or changing a setting when the page failed, confirm the action did or did not complete before doing it again. A failed page load never deletes anything, but it can leave you unsure whether a save went through.
If it keeps happening#
A page that keeps failing for several minutes is worth reporting. Note the exact error text, the page URL, the time it happened, and whether a hard refresh made any difference. Then open a support ticket with those details, so we can trace the failure instead of guessing.
Once the dashboard is healthy again, How to Set Up an Email Alias walks through creating your first forwarding alias.