Troubleshooting
This page covers common issues and how to resolve them.
Command Not Found
Unknown command: nemo
Symptoms:
nemo: command not foundUnknown command: nemo
Cause:
If you installed nemo-platform with pip or uv pip, it was installed in a virtual environment. The nemo command is only available when that environment is activated.
Solution:
Activate the virtual environment where you installed the package:
Installation Issues
Install Fails Building a Dependency
Symptoms:
uv tool install "nemo-platform[all]"fails while building a dependency, often on a missing C header such asomp.h
Cause:
NeMo Platform supports Python 3.12 and 3.13, but uv picks the interpreter itself, so an install can land on Python 3.14. nemo setup exits immediately on an unsupported interpreter instead of starting services.
Solution:
Name a supported interpreter. uv downloads one if you do not have it:
Connection Issues
Unable to Connect to Server
Symptoms:
Connection refusedorConnection timed outerrors- Commands hang or fail with network errors
Solutions:
-
Verify the base URL is correct:
-
Check that the server is reachable:
-
If running locally, ensure services are up:
Authentication Errors
Symptoms:
401 Unauthorizedor403 ForbiddenerrorsInvalid API keymessages
Solutions:
-
Verify your credentials are configured:
-
Re-configure the connection:
-
Check that your API key is valid and has the required permissions.
Debugging
Enable Verbose Output
Use the --verbose flag to see detailed information about what the CLI is doing:
This shows:
- API requests being made
- Response details
- Configuration values being used
Check Current Configuration
View your full configuration to verify settings:
Getting Help
- Use
--helpon any command for usage information - See the reference for complete command documentation
- See configuration for detailed configuration options