Skip to content
API MCP Server

Troubleshooting

Node.js Issues

Section titled “Node.js Issues”
Terminal window
node --version  # Must be 24+

If outdated:

Terminal window
# macOS
brew install node@24


# Linux
nvm install 24 && nvm use 24

npx Cache Issues

Section titled “npx Cache Issues”
Terminal window
npx clear-npx-cache
npx -y @robinmordasiewicz/f5xc-api-mcp

Configuration Issues

Section titled “Configuration Issues”
  1. Validate JSON syntax - use a JSON validator; common issues include trailing commas, missing quotes, and unescaped characters
  2. Check file path - ensure the config file location matches your OS (see IDE Setup)
  3. Restart application - completely quit and restart (not just close the window)

Authentication Errors

Section titled “Authentication Errors”

Invalid API Token

Section titled “Invalid API Token”
  1. Check token hasn’t expired
  2. Verify token was copied completely (no truncation)
  3. Ensure no extra whitespace

Certificate Error

Section titled “Certificate Error”
  1. Verify P12 file path is absolute
  2. Check password is correct
  3. Ensure certificate hasn’t expired

Connection Refused

Section titled “Connection Refused”
  1. Check URL format (see URL Normalization)
  2. Verify network connectivity to F5XC
  3. Check firewall rules

Unauthorized

Section titled “Unauthorized”
  1. Verify credentials have required permissions
  2. Check namespace access rights
  3. Ensure tenant URL matches credential’s tenant

Manual Credential Test

Section titled “Manual Credential Test”
Terminal window
curl -H "Authorization: APIToken $F5XC_API_TOKEN" \
  https://your-tenant.console.ves.volterra.io/api/web/namespaces

SSL/TLS Errors

Section titled “SSL/TLS Errors”

For staging environments and custom CAs, see the SSL/TLS Configuration guide.

Quick reference:

ErrorSolution
Hostname/IP does not match certificate's altnamesSet F5XC_TLS_INSECURE=true (dev only) or F5XC_CA_BUNDLE
self signed certificateSet F5XC_CA_BUNDLE=/path/to/ca-bundle.crt
certificate has expiredContact F5 XC admin
unable to verify the first certificateAdd intermediates to CA bundle

Common Error Codes

Section titled “Common Error Codes”
ErrorCauseSolution
ECONNREFUSEDNetwork issueCheck URL and connectivity
401 UnauthorizedInvalid credentialsRefresh token or check cert
403 ForbiddenInsufficient permissionsCheck RBAC settings

Server Not Starting

Section titled “Server Not Starting”
  1. Test command manually: npx @robinmordasiewicz/f5xc-api-mcp
  2. Check Node.js version: node --version (must be 24+)
  3. Verify npx is available: which npx

Environment Variables Not Set

Section titled “Environment Variables Not Set”
  1. Check for typos in variable names
  2. Ensure values don’t contain unescaped characters
  3. Try hardcoding values temporarily to test
  4. Verify with: env | grep F5XC

MCP Protocol Test

Section titled “MCP Protocol Test”

Verify the server responds to MCP protocol:

Terminal window
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"capabilities":{}}}' | npx @robinmordasiewicz/f5xc-api-mcp

Getting Help

Section titled “Getting Help”