This article covers troubleshooting steps for when a Finalsite-hosted site shows errors or fails to load, including how to check server status, test site availability from multiple locations, and diagnose DNS configuration issues.
💡Quick answers
- What is the first thing to check when a site is down? Check the Finalsite Server Status page to see whether the server hosting the site is currently up or down.
- Can automatic notifications be set up for server status updates? Yes. Click Subscribe to Updates on the Server Status page to receive email, text, or Atom/RSS notifications.
- How can an outage be tested as local vs. global? Use Uptrends' Uptime Tool to test the site from multiple locations around the world and compare results.
- Why is the site only unreachable from the school network? This usually points to a DNS issue localized to that network. Run a DNS check with Pingdom Tools and contact IT support if the site loads from elsewhere.
- What causes a 503 Service Unavailable error? It can result from a Finalsite data center issue, a local network problem, a DNS configuration error, or another cause entirely.
- Why is the site unreachable for everyone when the Finalsite Status page shows no issue? The domain's name server may be offline. DNS lookups fail before the request reaches Finalsite, so no incident is posted. Contact whoever hosts your domain's DNS (your registrar, IT team, or a state or district agency) first.
Troubleshoot a site that won't load
Consistent site errors, long load times, or 503 Service Unavailable errors can result from a number of factors: an issue at the Finalsite data center, a network connectivity problem at or near the school, a DNS configuration error, or something else entirely. Work through the steps below to narrow down the cause.
Check the Finalsite Server Status page
Visit the Finalsite Server Status page to check whether the server hosting the site is currently up or down. The page is updated manually by Finalsite based on data center diagnostic monitors, which means it provides a definitive answer about any known issues. If a notice about a server cluster appears there, the team is already aware and working on it.
- To receive automatic notifications about future status updates, click Subscribe to Updates on the page and select email, text, or Atom/RSS as the preferred format.
- The Status page also includes post-incident notes about past downtime events. For questions about a previous outage, check there for a breakdown of what occurred.
Test site availability from multiple locations
If the Status page shows the server as up but errors persist, use Uptrends' Uptime Tool to test the site from multiple locations around the world. Uptrends displays all results including ping times, which can help identify whether a local outage is preventing access when no server-side issues exist.
Run a DNS settings check
If Uptrends indicates the site is up but it still cannot be accessed, use Pingdom Tools to run a DNS health check. This test verifies whether the site's domain is pointing to the correct IP address for the Finalsite data center. When entering the domain, leave off the www. prefix.
DNS issues can be localized to a specific network. If the site loads from a device outside the school network but not from on-campus, contact IT support and let them know the DNS configuration may need to be reviewed.
Site is unreachable everywhere but the Status page shows no issue
Every domain has a name server, the server that holds the domain's DNS records. When someone enters your address in a browser, their device first asks that name server where the site lives, and only then connects to Finalsite. If the name server is offline or misconfigured, the lookup fails and the request never reaches Finalsite. That is why the Status page can show no incident while the site is unreachable.
Signs that this is the cause:
- The browser error mentions a DNS lookup, "server not found," or "this site can't be reached."
- Uptrends reports the site as unreachable from every location, and the Pingdom DNS check reports errors or cannot find the domain.
The name server is usually run by your domain registrar, your school or district IT team, or, for some domains (such as k12.xx.us, .edu, or .gov), a state agency or contractor. Contact whoever hosts your domain's DNS first. If Finalsite manages your DNS, or you are not sure who does, contact Finalsite Support and include your Uptrends and Pingdom results.
Contact Finalsite Support
If the steps above do not resolve the issue, contact Finalsite Support for further investigation.