Troubleshooting

Purpose: Help you identify and resolve common issues when connecting an AI assistant to Digi Remote Manager using the MCP server.

Confirm the baseline prerequisites and requirements.

Requirement

Check

How to verify

Digi Remote Manager administrator account access

API key access enabled.

In Digi Remote Manager, see if you can create an API key.

APIClosed Application Programming Interface credentials

Valid API key ID and secret.

In Digi Remote Manager, view the API keys list.

MCPClosed Model Context Protocol client

MCP-compatible AIClosed Artificial Intelligience client installed.

Any client or framework that supports the MCPClosed Model Context Protocol can connect to the Digi Remote Manager MCP server. See the Prerequisites for a list of MCP-compatible AI clients.

Network access

Outbound HTTPSClosed Hypertext Transfer Protocol Secure to Digi Remote Manager MCP endpoint.

Test connectivity to https://remotemanager.digi.com/mcp.

If any of the above prerequisites and requirements are not met, correct them before proceeding.

Possible cause

Verification step

Solution

MCPClosed Model Context Protocol configuration JSONClosed JavaScript Object Notation syntax error

Validate JSON configuration file in your AI client.

Correct the syntax; use a JSON linter.

Incorrect MCP endpoint URLClosed Uniform Resource Locator

Check that the MCP URL is https://remotemanager.digi.com/mcp.

Update the configuration with the correct URL.

AIClosed Artificial Intelligience client not restarted

Confirm that the client was fully exited and reopened.

Quit the application fully and relaunch.

Possible cause

Verification step

Solution

Incorrect APIClosed Application Programming Interface Key ID or secret

Recheck saved credential values.

Re-enter correct values; avoid extra spaces.

API revoked or expired

In Digi Remote Manager, view the API keys list and check its status.

Create a new API key and update the AIClosed Artificial Intelligience client.

Permissions insufficient

Confirm user role and API key permissions.

Assign appropriate Digi Remote Manager permissions.
MCPClosed Model Context Protocol

Possible cause

Verification step

Solution

Firewall or proxy blocking outbound HTTPSClosed Hypertext Transfer Protocol Secure

Attempt to reach the endpoint via curl or browser.

Allow outbound HTTPS to remotemanager.digi.com:443.

Local network restrictions

Test network access from host running the AI client.

Configure proxy settings or allow network egress.

Node.js or mcp-remote bridge issues

Verify Node.js version and CLIClosed Command Line Interface availability.

Install or update Node.js and required packages.

Possible cause

Verification step

Solution

Invalid query syntax

Compare with documented query examples

Use get_query_syntax_help and example templates.

Signed out or session timed out

Check AIClosed Artificial Intelligience client logs for authentication errors.

Reauthenticate by restarting the client or reloading credentials.

Data access permissions missing

Attempt tools requiring broader access.

Update APIClosed Application Programming Interface key permissions in Digi Remote Manager.

Possible cause

Verification step

Solution

No matching data for query

Run a broader query (e.g., list_devices).

Adjust query filters or provisions.

Account or subaccount scope issues

Review the account context used by the APIClosed Application Programming Interface key.

Ensure API key belongs to the correct account and scope.

Tip If the above steps don't resolve your issue, contact Digi Technical Support.

Make sure to have the following information available:

  • AI client used

  • API key ID

  • Configuration file contents (excluding sensitive values)

  • Exact error messages

  • Collect network logs showing connection attempts to the MCP endpoint.

  • Record the Digi Remote Manager account ID and scope of API key permissions.