The great folks at Nightscout recently published an update to members/subscribers regarding another breaking Mongolabs change. 
In a nutshell, recently, Mongolabs updated their MongoDb database to 3.0.7 which appears to be breaking Nightscout and other clients. My guess is that the fix recommended below ensures any pooled and or unauthenticated connections are released, but I haven’t dug deeper to verify.
If you host your Nightscout Website or Bridge on Heroku, keep reading. My intent in this post is to provide a simple way to restart your app without a lot of technical experience required.
If you are hosting the Nightscout Website or Nightscout Bridge on Heroku, you may stumble to figure out how to ‘restart’ the apps, called “Dynamos” (Step 2 on the right). On Microsoft Azure, it’s very simple to restart an Azure Website but Heroku is a bit more subtle.
A few Google searches reveals the heroku restart command line command, but I doubt most NightScout users are going to take the time to download client SDKs, set up Procfiles, etc. and there does not appear to be any documented way to restart a Dyno from the UI/Dashboard.
Poking around a bit, I found the solution is simple:
1. Click on your Dyno (i.e. this will be the app that is either running your Website or Bridge) to bring up the setting page.
2. On the settings page, Click Edit:
3. Once in “Edit” mode, you can switch your Dyano off
4. Be sure to hit Save.
5. Repeat Steps 2 and 3, turn the Dyno back on and hit Save.
Note, I did not have to wait 10 minutes for the fix to take effect. You should be able to refresh your website and it should work.
Hope this helps anyone needing to “restart” a Dyno. If it doesn’t work for you, please drop me an email or hit me up on twitter: @rickggaribay