Troubleshooting¶

This page covers common issues and how to resolve them.

Command Not Found¶

Unknown command: nemo¶

Symptoms: - nemo: command not found - Unknown 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:

source /path/to/venv/bin/activate

Connection Issues¶

Unable to Connect to Server¶

Symptoms: - Connection refused or Connection timed out errors - Commands hang or fail with network errors

Solutions:

Verify the base URL is correct:
```
nemo config view
```
Check that the server is reachable:
```
curl <your-base-url>/health
```

If running locally, ensure services are up:

curl -s http://localhost:8080/health/ready

Authentication Errors¶

Symptoms: - 401 Unauthorized or 403 Forbidden errors - Invalid API key messages

Solutions:

Verify your credentials are configured:
```
nemo config view
```

Re-configure the connection:

nemo config set --base-url https://nmp.example.com
nemo auth login

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:

nemo --verbose workspaces list

This shows: - API requests being made - Response details - Configuration values being used

Check Current Configuration¶

View your full configuration to verify settings:

nemo config view

Getting Help¶

Use --help on any command for usage information
See the reference for complete command documentation
See configuration for detailed configuration options