Troubleshooting¶

Package Not Found¶

If pip cannot find the package, verify:

Your pip configuration includes the Artifactory extra-index-url
Your Artifactory credentials are correct
You have access to the nautobot-mcp-server repository

Test Artifactory access:

curl -u <USERNAME>:<API_TOKEN> https://nautobot.jfrog.io/artifactory/api/pypi/nautobot-mcp-server/simple

Command Not Found¶

If nautobot-mcp-server command is not found after installation:

Verify the package is installed: pip list | grep nautobot-mcp-server
Check that your Python scripts directory is in PATH:
```
python -m site --user-base
```
Add <user-base>/bin to your PATH if needed
Try running via Python module:
```
python -m nautobot_mcp_server.server
```

Connection Errors¶

If the server cannot connect to Nautobot:

Verify NAUTOBOT_BASE_URL is correct and accessible
Verify the user's Nautobot API token is valid (test in Nautobot UI or via REST API)
Check firewall rules allow outbound HTTPS connections
If using self-signed certificates, set NAUTOBOT_VERIFY_SSL=false (not recommended for production)

Systemd Service Won't Start¶

Check the logs:

sudo journalctl -u nautobot-mcp-server -n 50

Test manually as the service user to see errors directly:

sudo -u nautobot-mcp bash
cd /opt/nautobot-mcp-server
/opt/nautobot-mcp/.local/bin/nautobot-mcp-server

Check file permissions:

ls -la /opt/nautobot-mcp-server/
ls -la /opt/nautobot-mcp/.local/bin/nautobot-mcp-server

Systemd Service Stuck in Failed State¶

sudo systemctl reset-failed nautobot-mcp-server
sudo systemctl start nautobot-mcp-server

Common causes: - Invalid NAUTOBOT_BASE_URL or user's Nautobot API token - Network connectivity issues to Nautobot - Port 8000 already in use - Incorrect ExecStart path in the service file