Troubleshooting self-hosted Neptune#
This page lists problem situations related to self-hosted Neptune and how to work around or solve them.
See also the FAQ →
New runs not showing up in web app#
Issue: New experiments are not showing up in the runs table, but can be accessed via direct URL.
Solution: If you're running low on disk space, Neptune may not be able to index new runs.
Important
Make sure to check the usage of the Neptune-dedicated disk, not other disks (such as the system disk).
How to send data to Neptune#
Your currently used domain is encoded into the token itself. The place where you run your Neptune client library just needs to know how to resolve this domain.
To find and copy your API token:
- Log in to the web interface of your self-hosted installation of Neptune.
- In the bottom-left, open the user menu → Get your API token.
- Use the token with the Python client library. For help, see Set your API token.
Note
We strongly recommend using HTTPS (SSL certificates) when exposing Neptune. If you want to use HTTP or you have a self-signed certificate, exporting some environmental variables might be required for the client to work properly.