Troubleshooting#

This page covers common issues and how to resolve them.

Command Not Found#

Unknown command: nmp#

Symptoms:

nmp: command not found
Unknown command: nmp

Cause:

If you installed nemo-microservices with pip or uv pip, it was installed in a virtual environment. The nmp 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:
```
nmp config view
```
Check that the server is reachable:
```
curl <your-base-url>/health
```
If using quickstart, ensure it’s running:
```
nmp quickstart status
```

Authentication Errors#

Symptoms:

401 Unauthorized or 403 Forbidden errors
Invalid API key messages

Solutions:

Verify your credentials are configured:
```
nmp config view
```
Re-run the configuration wizard:
```
nmp configure
```
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:

nmp --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:

nmp config view

Getting Help#

Use --help on any command for usage information
See the Full CLI Reference for complete command documentation
See Configuration for detailed configuration options