If you find that you are unable to access your storefront or experience any of the errors below, there may be an issue with your DNS settings. We've gathered a list of common issues and their solutions to help you get back into your store.
Follow these steps if you or your customers are unable to access your storefront, or if you are unable to access your control panel after logging in. If you recently pointed your domain to BigCommerce, note that it can take up to 72 hours for the change to take effect.
1. Check status.bigcommerce.com for any issues we may be experiencing on our end.
2. Are you able to log in to your store?
- Yes — follow the steps below
- No — please reach out to our Support Team for assistance
3. If you are using a custom domain for your store, verify that it has been pointed to BigCommerce using one of the methods described in Changing Domains.
- You can use free online tools from sites such as centralops.net to confirm that your domain is correctly pointed.
- If you pointed your domain with an IP address/A record and recently changed to or from a dedicated SSL certificate, your IP address will have changed. See the instructions in Finding Your Web Address to verify your domain is correctly pointed.
4. If you are not using a custom domain for your store (i.e. your domain ends in .mybigcommerce.com), and have made one of the following domain changes, it may take a few minutes for your changes to take effect.
- Changed your domain from one .mybigcommerce.com domain to another .mybigcommerce.com domain
- Changed your domain from a custom domain to a .mybigcommerce.com domain
If it has been more than 15 minutes since the change, try clearing your browser's cache and cookies by following the steps listed for your browser at refreshyourcache.com.
A 404 error indicates that the page that was requested is not available on the site it is being requested from. This often happens when you are attempting to access a page that was recently deleted, or that moved to another URL. The most common error messages you'll encounter are:
- 404 Error - Page Not Found
- Uh oh, looks like the page you are looking for has moved or no longer exists.
- The page you were looking for appears to have been moved, deleted or does not exist.
- We cannot find the page you are looking for.
Troubleshooting 404 Errors
Note that if you have deleted a page, you want a 404 page to display when someone attempts to access its old URL. This informs both your customers and search engines that the content is no longer available. Search engines will eventually drop the URL from their index and will no longer attempt to crawl it.
1. Refresh the webpage, or try the URL from the address bar again.
A 404 could appear for a variety of reasons even when things are working as they should, so sometimes a refresh is all you need.
2. Doublecheck the URL.
Often, a 404 will appear because the address was mistyped or the link that was used had the wrong URL.
3. Clear your browser's cache and cookies.
Browsers will save pieces of sites that you visit to speed up your loading the next time you stop by. Sometimes these pieces of information can get corrupted, causing all sorts of browser issues not related to the site that you were trying to visit. It's always a good idea to clear your browser on a regular basis.
4. Move up a level in the link hierarchy.
For example, if a particular product page gave you the 404 error, move up to the category. If you can navigate to the category, try visiting the product directly from there. This should lead you to what you're looking for or confirm where the issue might be.
If the links that you're using are bookmarks or links from other pages in your store, be sure to update them to avoid others stumbling into a 404. This often happens when you've changed a products name or changed the name of a content page. Enabling automatic redirects will help avoid broken links from happening. If you'd like to create your own redirects, see 301 Redirects for more information.
A 502 error page indicates that there was an issue between two servers online that were attempting to communicate with each other. Generally, this is unrelated to anything on your end. The most common error message you'll encounter is:
- 502 Bad Gateway / nginx
Troubleshooting 502 Errors
1. Check status.bigcommerce.com for any issues BigCommerce may be experiencing.
The status page is updated in real time and is the best source for the latest issue updates or developments. If you see an issue reported there, be assured our engineering and technical operations team are aware and are currently working to address it.
2. Refresh the webpage.
As with any page error, one of the first steps is to try a page refresh. Often 404s or 502s are temporary and are resolved as quickly as they appear.
3. Close all of your open browser windows and start a new session. Then, try the page again.
It's possible the 502 error you encountered was due to network issues your computer experienced during your browser session. This can happen even without you realizing it. A simple restart of your browser could solve the issue.
4. Clear your browser's cache and cookies.
If a browser restart does not resolve the issue, then the files your browser was storing could be out of date or corrupted. Removing these files and revisiting the page will solve the issue.
5. Try a different web browser.
The most popular browsers are Chrome, Internet Explorer, Safari, and Firefox. If the alternative browser does not produce the 502 error, you know that your primary browser is the source of the issue. If you've already cleared your cache and cookies, it might be time to reinstall the browser. Additionally, try to visit the page on a mobile device not connected to your network.
6. Restart your computer.
If you see this error on more than one website, your computer may have issues connecting to your network. A restart could help.
7. Restart your network.
If you continue to see 502 errors, there may be an issue with your network equipment (e.g modem, router). Restart them from the outside in (e.g modem, router, computer).
8. Contact your Internet Service Provider (ISP).
If you've exhausted all the troubleshooting steps so far, then your ISP could be the cause of the 502 issues.
If all else fails, reach out to our Support Team for additional assistance.