Skip to main content
If you run into a problem not listed here, try asking the local AI in the AI Chat (accessible from the Command Center home screen) or join the community on Discord.
Some services take extra time to start, especially after a restart or update.Try these steps in order:
  1. Wait 30 seconds — the service may still be initializing
  2. Refresh the page (Ctrl+R or Cmd+R)
  3. Go back to the Command Center home screen and try again
  4. Check Settings → System to see if the service shows as running
  5. Go to Settings → Apps, find the service, and click Stop then Start
If the service still won’t load after a restart, check Settings → System for error messages.
The Maps feature requires downloaded map data. A blank or gray map means no map data has been downloaded for that region.
  1. Go to Settings → Maps Manager
  2. Download map regions for your area
  3. Wait for the downloads to complete
  4. Return to Maps and refresh the page
Local AI inference is computationally intensive. Several factors can affect speed:
  • No GPU — CPU-only inference is significantly slower. An NVIDIA GPU with the NVIDIA Container Toolkit can improve AI speed by 10–20x or more. See GPU Acceleration.
  • Other apps competing for resources — close applications running on the server that aren’t needed
  • Thermal throttling — ensure the server has adequate cooling; overheating causes the CPU or GPU to reduce its speed
  • Model size — larger models produce better responses but run slower. Consider switching to a smaller model if speed is a priority.
Document processing takes time, especially for large files.
  1. Check that the AI Assistant is running in Settings → Apps
  2. Large documents can take several minutes to process — wait before assuming it’s stuck
  3. Try uploading a smaller document to confirm the system is working
  4. Check Settings → System for any error messages
If uploads consistently fail, verify that the AI Assistant is fully installed and not showing any errors.
To submit a score to the community leaderboard, all of the following must be true:
  • You must run a Full Benchmark — not System Only or AI Only
  • The AI Assistant must be installed and working (AI results are required)
  • Your score must be higher than any previous submission from the same hardware
If submission fails, check the error message displayed after the benchmark completes for more specific details.
The service may still be starting up, especially after a system restart.
  1. Wait 1–2 minutes and try again
  2. If it persists, go to Settings → Apps
  3. Find the affected service and click Restart
  4. Wait 30 seconds, then try accessing the service again
  1. Check your internet connection — downloads require internet access
  2. Go to Settings and check available storage
  3. If storage is full, delete unused content to free up space
  4. Cancel the stuck download and try again
If a download notification persists after a failure, you can dismiss it from the downloads panel.
If you cannot access the Command Center at http://SERVER_IP:8080 at all:
  1. Verify the server hardware is powered on
  2. Check that the server is connected to the network
  3. Try accessing via the server’s IP address directly (instead of a hostname)
  4. If you have console access, check the Docker container logs for errors
You can also use the command-line helper scripts in /opt/project-nomad:
sudo bash /opt/project-nomad/start_nomad.sh
Kolibri manages its own user accounts separately from N.O.M.A.D.
  • If you are a Kolibri admin: Reset other users’ passwords from Kolibri’s user management panel
  • If you forgot the admin password: You will need to reset it from the command line. Contact your server administrator or refer to the Kolibri documentation for the password reset process.