When your website won't load at your own domain (for example, yourleague.org), the TeamSideline site itself is usually still running: the domain isn't pointing to it, the domain expired, or the site was turned off. Try your site's TeamSideline address first, then work through the checks below.
Applies to: Admins · All plans · Legacy content editor and Editor 2.0 websites
Where: Your site's TeamSideline address; Help > System Status in the admin menu; Administration > Subscription
First, try your site's TeamSideline address
Your site also has a TeamSideline address. Use it to keep taking registrations and running your season while the domain is fixed.
- Editor 2.0 websites: https://yourleague.teamsidelinesite.com, with your site's name in place of yourleague.
- Legacy websites: https://teamsideline.com/sites/yourleague/
- Admin Sign In, for either editor: https://teamsideline.com/sites/yourleague/admin/sign_in
If your own domain is set up as your site's main address, the teamsideline.com addresses send you on to it, so they won't load while it's down. Ask support to switch your site back to its TeamSideline address until the domain is fixed. If you don't know your site's name in these addresses, support can tell you.
Check these, in this order
- Check System Status: in the admin menu, click Help > System Status, or go to https://status.teamsideline.com. If an incident is posted, TeamSideline is working on it, and your TeamSideline address may not load either.
- Try your TeamSideline address. If it loads, your site is running and the problem is with your domain. If it sends you on to your own domain, ask support to switch it back (see above).
- Try another browser, a private window, or another network such as mobile data. This rules out a cached error or a block on one network.
- If you have more than one domain (for example, yourleague.org and yourleaguefc.org), try each one. If only one fails, the problem is with that domain.
- Note the exact message on the page, and take a screenshot that shows the address bar.
- Ask whoever manages your domain whether anything changed recently at your registrar (such as GoDaddy or Namecheap): the nameservers, the A or CNAME records, the renewal, or email setup done by an IT contractor.
What you'll see, and what it means
| What you see | Likely cause | What to do |
|---|---|---|
| Your domain and your TeamSideline address both fail, and System Status shows an incident | A TeamSideline outage or maintenance. During maintenance the page says "TeamSideline is temporarily offline." | Follow the updates on System Status. |
| Every TeamSideline page, including Admin Sign In, opens the TeamSideline home page instead of your site, and an Editor 2.0 website goes offline | Your site was turned off because the TeamSideline subscription was canceled, usually for an unpaid invoice. Your organization's Contact Us email address gets "Your TeamSideline site has been deactivated". | Pay the invoice from your invoice email or the billing portal. The site turns back on automatically when the payment is received. Contact support@teamsideline.com if you need help. |
| Only your domain fails; your TeamSideline address works | The domain isn't pointing to TeamSideline: the nameservers or DNS records changed, the domain expired, or a change is still spreading. | See "Fix a domain that isn't reaching your site" below. |
| A page titled "Invalid Domain" that says "The domain name you attempted to access is not setup correctly or is not supported." | The domain reaches TeamSideline but isn't connected to your site, for example after a new website went live. You also see this page while your site is turned off after a canceled subscription; your TeamSideline address then opens the TeamSideline home page instead of your site. | Contact support, who connect the domain to your site. If your site was turned off, pay the invoice, and the page goes away once the site turns back on. |
| An access-denied or 403 Forbidden page on one network, while other networks work | TeamSideline's security protection blocked traffic from that network. | Send support the error, the time and the network you were on. Support can have the block lifted. |
| A "Not secure" or certificate warning right after a domain change | The site's security certificate hasn't been issued yet. | Allow up to 24 hours after the DNS is correct, then contact support if it continues. |
Fix a domain that isn't reaching your site
- The nameservers were changed. This is the most common cause, often while someone was setting up email. Ask support which nameservers your domain should use, and enter exactly those at your registrar in place of the others. If TeamSideline manages your domain's DNS, ask support to add the email records you need rather than changing the nameservers.
- Your organization manages its own DNS. Support gives you the A and CNAME records your site needs. Add them at your registrar or DNS host.
- The domain expired. Renew it at your registrar, and the site comes back at that address once the domain is active again. If you're letting the domain go, ask support to remove it from your site so visitors use your TeamSideline address.
- A new website just went live. After a move to Editor 2.0 or another go-live, a domain can be left off the new site. Support connects it on TeamSideline's side. An Editor 2.0 website also needs its security certificate issued, which can take up to 24 hours.
- A change is still spreading. DNS changes can take 24 to 48 hours to reach everyone. Clear your browser cache before you test again.
How to get help
Email support@teamsideline.com, or click Help > Contact Support in the admin menu, and include:
- The domain or domains that don't load.
- A screenshot of the error that shows the address bar.
- Whether your TeamSideline address loads.
- Who manages your domain, and anything that changed recently at your registrar.
- For an access-denied page, when it happened and which network you were on.
Good to know
- Never send your registrar password or a verification code to support. For help with a change at your registrar, ask support for a screen share, or give your webmaster access through your registrar's own delegate or account-sharing feature.
- TeamSideline doesn't have your registrar login. If no one at your organization can sign in there, use the registrar's account recovery.
- A domain that stops loading doesn't affect your site's data, registrations or schedules. Everything is still there at your TeamSideline address.