FAQ – Nightscout Hosting ns.10be.de | xDrip, AAPS, Loop, Betaling & meer

We offer Nightscout purely as a data storage / diary / information management software, which currently does not require approval.

Previously, the servers were largely sponsored, but this was discontinued at the beginning of the year :-(

As a result, the servers now have to be paid for after 5 years, which is not affordable privately, and the total donations don't even cover 10% of the costs.

Did you receive an email from PayPal saying that your profile is no longer active and the subscription payment has been cancelled?

Then you probably completed the subscription before September 19th, when there was a configuration error that caused the cycle to be only 1, 3, 6, or 12.

In this case, please log in to ns.10be.de Payments and complete the subscription again.

If an amount has already been debited, please send me your PayPal email address so that the amount can be refunded.

The server will be deactivated, but not immediately deleted. Your data is preserved.

You can add a new payment at any time to reactivate the server. This can be done via Payments in the dashboard.

There is no limit. However, each instance requires an active payment, otherwise the instance(s) cannot be used.

For example, if you want to use two instances and don't want to pay in advance, you need to pay 2 x €4.99 = €9.98.

You have 15 instances but only 10 payments, so you can only use 10 servers simultaneously.

Yes! From the 2nd server onwards, you automatically receive a 25% discount via coupon code. The code is shown when creating an additional server.

You also save with longer payment intervals: With 12 months prepayment you save about 20% compared to monthly payment — plus DB export included.

The instance can only be used if payment has been made.

If you're not using the instance, you can cancel the subscription at the end of the term and only pay again when you want to use Nightscout again.

Yes, they will be deleted within a few seconds.

However, a backup of the MongoDB and MySQL database exists for up to 3 days, so the data can be restored with significant effort.

After those days, when the backups have been overwritten, no data remains and everything is completely deleted from the server/account.

The Nightscout profile is configured directly inside your Nightscout instance — not in the ns.10be.de dashboard.

Steps:

1. Open your Nightscout URL (e.g. your-name.ns.10be.de)
2. Click the menu (≡) top right and select Profile Editor
3. Enter your values:
   • Timezone
   • Insulin duration (DIA)
   • Insulin sensitivity factor (ISF)
   • Carb ratio (CR)
   • Basal rates (units per hour, by time of day)
   • Target range (low and high values)
4. Click Save and then Activate — without activation the profile is inactive!

Master is the stable, recommended version for most users.

dev-psonnera is a customized variant with additional AAPS features (e.g. SMB visualization) — recommended for advanced AndroidAPS users.

You can switch the branch at any time in the server editor. After saving, the server will automatically restart with the new branch.

Please contact us. Theoretically this is no problem, unless the change needs to go into my.env. This file is recreated after editing the server in the profile.

Simply click "Redeploy" in the server overview. Your server will restart with the latest Nightscout version.

The server overview also shows you directly whether your version is up to date or if an update is available.

For major updates (e.g. major versions), we update all servers automatically.

Yes, unless you have enabled the "withoutport" option, then you can access the instance without the port using just https://xxxx-your-name-xxxx.ns.10be.de/

Yes! In the server editor, there is the "Custom Configuration" section. There you can add any Nightscout environment variables as key-value pairs.

Examples: CUSTOM_TITLE, THEME, SHOW_FORECAST etc.

You can also use a custom Docker image, e.g. if you want to test your own Nightscout fork.

Please enable the "withoutport" option, then the instance is also accessible directly via https:// without the port.

You can also contact us and we can manually assign a port to you.

Check the timezone in the Nightscout profile and correct it. Then create the reports again.

This problem can occur due to profile switching and is known: https://github.com/nightscout/cgm-remote-monitor/issues/3659

If the instance shows "running", please wait another 10 minutes, then it should work again.

If it still doesn't work after 15 minutes, please edit the instance and save it again or click "redeploy", then it should work again.

If it still doesn't work, please contact us.

This is a local DNS problem. Simply restarting the phone usually helps. If the message still appears, restart your DSL router as well.

On Linux, for example with the following command: mongorestore -h dsXXXXXX.mlab.com:XXXXXX -d databasename -u username -p dbpassword /your/path/dbbackup/nightscoutXXXX/

Alternatively, you can use DB Export to import the database directly into another database for a fee.

ns.10be.de supports multiple import methods directly in the dashboard:

• API Import — Nightscout to Nightscout, simply enter the source URL and API secret
• MongoDB Import — Upload a complete DB dump (e.g. from Atlas/mLab)
• CSV Import — For Omnipod, Freestyle Libre and Dexcom data

Go to Import in the dashboard and choose the appropriate method.

This can happen if either the login credentials are wrong or a pump newer than the 640G is being used.

With Dexcom US, problems can occur that appear in the Server.log as "Error refreshing token null 500 Code: 'SSO_AuthenticateMaxAttemptsExceeed', Message: `Synchronization of SSO account during login failed. AccountId=......."

See this post on FB

First log in to mlab/mongodb: https://account.mongodb.com/account/login.

1. Click on "Database" on the left, then 2. click "Connect" on the right.

3. Then click "Connect with mongodb shell".

4. Copy the part between "mongodb+srv://" and "/myFirstDatabase".

Something like cluster0.7fhhjbf.mongodb.net is your Mlab DB Host.

The database name, username and password should be known to you. Otherwise you can find them in the Heroku "vars".

Then activate the "Mlab ATLAS" checkbox, select the target instance and save.

If it doesn't work, please contact us. We'll help you.