Overall third party services⌁
APPLIES TO: DIY Nightscout
For Nightscout as a service contact directly support at t1pal.com or use the
Get Support links.
Check the services you're using.
Carelink US: https://carelink.minimed.com/
Carelink non-US: https://carelink.minimed.eu/app/login
GitHub and Heroku⌁
A valid GitHub Directory could not be found.⌁
When trying to deploy a new Nightscout site, this message appears when clicking
Deploy to Heroku.
- Change browser and retry.
I lost access to my GitHub⌁
Create a new account and fork cgm-remote monitor as described here.
Follow only Step 1.
You can now upgrade or redeploy your Nightscout using redeploy as explained here. You won't have to delete the existing repository since it's not there for the moment. Go down to Fork cgm-remote-monitor in the explanation.
Cannot find cgm-remote-monitor in Heroku / No GitHub source visible⌁
When updating Nightscout,
cgm-remote-monitor doesn't appear automatically in Heroku under your repository name.
When updating Nightscout, your repository name doesn't appear in
Manual Deploy so that you can't select the
- If it doesn't help try to re-authorize as explained below:
Cannot find cgm-remote-monitor in Heroku: Item cannot be retrieved⌁
When updating Nightscout,
cgm-remote-monitor doesn't appear automatically in Heroku under your repository name and an error message appears when you try to connect to GitHub.
- In Heroku, go to
Authorize GitHubin the pop-up.
- If it doesn't help, you can also try to
Revoke access... before going back to Re-
Connectyour GitHub account. This is necessary if someone else did setup Nightscout for you and left his own GitHub connected to your Heroku account.
I can't log into Heroku⌁
If you lost your password use the password reset option.
If you lost your authenticator use the recovery codes (that you hopefully saved when securing your account).
If you lost or don't have anymore access to the email you used to create your Heroku account you will need to deploy a new Nightscout site. You can use the same GitHub account and the same MongodB Atlas database you currently have but will have to use another Nightscout site name in Heroku as the current one is already in use. First recover your connection string, and proceed to creating a new Nightscout skipping Step 3.
Limit of one free cluster.⌁
When creating a new site or migrating (usually not the first attempt), when reaching
- Click the leaf top left in your Atlas account. Look at the
Project Nameyou wanted to use when creating your new cluster, it shouldn't contain a cluster yet (like the example below, I tried to create a new Nightscout site but there is already a cluster inside the project I wanted to use). You can't have two clusters in a free project. Click your
- This should not happen in normal conditions. Before deleting a cluster, check it doesn't contain your data!
- Click on
Collectionsin the cluster you selected.
- Click on
- In the case there is data, like in the example below, don't use this cluster. Leave it like this and create a new one.
- If there no data, you can safely delete it.
- In this cluster you want to delete click
- Copy the cluster name to confirm then click
- Wait until the operation completes.
- You can now use this project name to create a new site.
Nightscout page doesn't open⌁
Update Nightscout to latest release. It might not fix your issue but it will help find a solution.
- If you didn't migrate your Heroku database from mLab to Atlas create a new Atlas database.
- If you didn't migrate from Azure to Heroku create a new site create a new Nightscout site with Heroku.
If you don't see any good reason just go ahead:
Restart all dynos⌁
- Log in Heroku, go to
Restart all dynos.
Nightscout stopped working after a few weeks⌁
Same screen than above but you received a mail from Heroku telling you you're out of dyno hours...
Check your remaining dyno hours in Heroku, click on your profile picture top right and select
Account Settings, then
An account without credit card information has 550 free dyno hours, with credit card information 1000.
- An account with credit card information can only hold one Nightscout site. You need one account per site, and you can simplify multiple sites management as explained here.
- If Heroku runs out of free dynos, check you don't have other deployments wasting your free dyno hours and eventually cleanup or stop unused apps.
Boot Error - Unable to connect to Mongo⌁
Look at this dedicated page.
No data in Nightscout⌁
Make sure your Nightscout time zone is correct.
Dexcom data not showing⌁
Make sure you have Dexcom Share turned ON in your Dexcom app. In the Dexcom app's main screen, find the triangle made of dots. If the dots are grey, you do not have Share turned on. Tap the triangle, and follow the directions to add a follower (yourself if you don't have someone else you'd like to invite) and turn on Share.
If you are using a Dexcom system, and your data is not appearing in Nightscout, there are only a limited number of reasons for that. You should check your (1) Heroku settings and (2) Dexcom Share.
NOTE: The #1 reason why BGs aren't showing is that you have mismatched password and user names in Heroku settings and Dexcom.
Login to your Heroku account and from within Heroku
Settings, click on the
Reveal Config Vars
Now from the
Config Vars area, check the following (see screenshot below for reference):
- You must use the same
BRIDGE_USER_NAMEthat your Dexcom mobile app is using.
- You must have
ENABLEline (you can have other values there...but don't forget these two).
- If you are outside the USA, you must add
EUin Heroku settings.
careportalmust be one word in the
ENABLEline, sometimes autocorrect makes it two words.
- If using
mmol, make sure you have spelled that value correctly in the
One thing that can happen if you have an incorrect Dexcom login/password in your Share account settings and/or in your Nightscout
BRIDGE settings is that Dexcom will lock your account...and you won't see CGM data in Nightscout. If you notice your CGM readings disappeared, but everything else is flowing...check your Heroku logs that are viewable by selecting "View Logs" from the drop-down menu underneath the "More" option.
Do your logs have "
SSO authentication errors" like in the red box highlighted above? If you do, then:
- Delete your
BRIDGEentries within Heroku settings. Don't delete the variables, just delete the values of
- Wait 15 minutes and then follow the directions below. It is important to wait 15 minutes: the reason you can't log in right now is that your Dexcom account has a temporary lock from the passwords in the step above being incorrect. The temporary lock will expire after 10-15 minutes of giving the account login a break from the incorrect logins. So, definitely wait or else you'll just keep prolonging the issue.
When you change these variables, Heroku restarts Nightscout. So now everything should work.
About your Bridge password and user name
The most common error on initial Nightscout setups is that people incorrectly use an old account or an old password. To test your username and password, go to Dexcom's Clarity page (check here for USA accounts and here for the others) and try logging in to your Dexcom account. If your account info isn't valid, or you don't see any data in your Clarity account... you need to figure out your actual credentials before moving ahead. See here for troubleshooting tips and information on your Dexcom account.
Dexcom username issue⌁
New Dexcom users are not being assigned a username anymore but need to log with their email address. If you don't have a username, you should be able to use
bridge with an email address, make sure you update Nightscout to the latest release.
Dexcom or CareLink data stopping after a while⌁
CareLink with mmconnect data source stopped functioning for most . Remove the
mmconnect plugin from
ENABLE if you use Heroku.
First verify you can see your BG in Clarity.
If data is present open Heroku and check you app didn't fall asleep.
A sleeping app might be due to your Heroku free plan: a Hobby plan makes the app never sleep. https://www.heroku.com/pricing
Another reason for a sleeping app can be due to a failure to obtain data from Dexcom Share, check the logs to understand the reasons.
Using an uptime robot with a bad password, or other issues originating from Nightscout can lead to a locked account (Dexcom) or Heroku addresses ban. This is not a recommended solution as it might generate a global Heroku IP blacklist lock that could propagate to all other users. If you use Nightscout, uploading data in the cloud or even just having a browser or an app downloading data should be enough to keep your app awake.
Error code instead of a BG value⌁
Nightscout implements Dexcom error codes as listed below:
||Sensor not active|
||Sensor not calibrated|
Data timing issues⌁
Basal is shifted in time⌁
- Check the time zone is correct for your currently active profile in your Nightscout
Data in the future⌁
- Check you don't have data in the future with the
Admin tools. Remove them if existing.
- If this isn't working, or shows no future data, check in Atlas
- Open your Nightscout cluster and select
- Delete the entries in the future (manually) with the bin icon
Basal / IOB / COB missing after DST⌁
- Setup again your time zone in profile editor (authenticate and save).
Free databases like M0 Sandbox provided by Atlas will only hold a limited amount of data (512MB) and you will eventually need to manually cleanup. You can extend the capacity to 2 and 5GB paying an M2 or M5 Shared cluster.
- Make sure your Nightscout site has
Database Sizeenabled to monitor database capacity. Look here for more information on this plugin.
- Check in Atlas
- Open your Nightscout cluster and select
- Click your database name (hidden left). Check the
DATABASE SIZEis indeed close to or at the limit then look at these three collections
- Open Nightscout
- Depending on the collection you identified above, choose which of the following you want to cleanup:
You can cleanup (enter the number of days to keep) or delete your devices status:
Glucose entries. If you are reluctant to lose historical data you should consider opting for a paid database solution.
Reports slow loading or timeout⌁
Loopers might experience Nightscout taking an extremely long time or even timing out when creating reports due to the profiles collection database growing too big.
Two solutions are available:
- Follow this video (set it full screen in 720p) to selectively delete profiles https://www.youtube.com/watch?v=iipp0MfPKNQ
- Delete all profiles in Atlas
Log in to Atlas https://account.mongodb.com/account/login
Select your cluster then
profile collection and click the bin icon to delete all profiles.
profile in the box then click
Open your Nightscout and create a new profile (mind the time zone!), authenticate and save it.
If you are using Loop, temporarily change a basal rate in Loop, and confirm your profiles now show up in Nightscout.