A white screen sometimes happens after a re-deployment or site update. If you are sure your white screen is not related to a mongo string error, typical during the creation of a new site, the following steps may be necessary to fix your site. These steps are listed in order of difficulty, from simplest to most extreme. We recommend trying them in order as you work to troubleshoot your site.
After each/any of these steps, you may need to wait a few minutes and then reload your site in a browser window to see if the site is working. In some cases, you may need to wait five minutes, or until the next data point, to determine if the site is working.
The first thing to do is to check the status of your site’s deployment. In Azure, click the “Deployments” tab and see if the most recent (top) deployment shows that it was Successful. If the deployment shows an error (or failure), start with #2 below.
- Restart your site in Azure. Directions to restart an Azure website in the new Azure portal appear here.
Direction for older Azure interface: Click the “Configure” tab and then click the “restart” button at the bottom. (Wait a few minutes, load your site, and see if the problem has resolved.)
- Redepoloy your site in Azure (or Heroku). See steps for “Simple Redeploy” here. (After reconnecting, the site will deploy. Once it deploys, wait a few minutes, load your site, and see if the problem has resolved.)
- If neither of the steps above solved your white screen, updating your site to Funnel Cake (if it is not already) may clear the problem. Some users have reported success by doing their update. Make sure you are logged in at Github, then use the Update My Fork tool linked from these directions: How to Update to Latest CGM-REMOTE-MONITOR Web Site. (Be sure and wait 5-10 minutes after updating to try the site. It can take that long before the site loads properly.
- Disconnect from Github in Azure, reconnect, and redeploy. (After reconnecting, the site will deploy. Once it deploys, wait a few minutes, load your site, and see if the problem has resolved.)
- Delete your fork in Github and refork. Then disconnect and reconnect in Azure.
- Recreate your site in Azure. (After the site deploys, wait a few minutes, load your site, and see if the problem has resolved.)