Troubleshooting

Common issues and their solutions.

Connection refused

Error: Unable to connect to http://localhost:3002. Is the server running?

Cause: The ActionXM server is not running or is unreachable.

Fix:

1. Verify the server is running: curl http://localhost:3002/health
2. Check your API URL: actionxm config get api_url
3. Update if needed: actionxm config set api_url https://your-server.com

Token expired

Token expired or invalid
Run actionxm auth login to re-authenticate.

Cause: Your JWT token has expired (tokens are valid for 7 days).

Fix: Re-authenticate:

actionxm auth login

Device code expired

Error: Device code expired. Please try again.

Cause: You didn't approve the device code within 15 minutes.

Fix: Run actionxm auth login again and approve promptly.

Permission denied

Error: HTTP 403

Cause: Your account doesn't have access to the requested resource.

Fix: Check your role with actionxm auth status. Contact your tenant admin if you need elevated access.

Config file permissions

If you see permission errors reading the config file:

chmod 600 ~/.config/actionxm/config.json
chmod 700 ~/.config/actionxm

Browser doesn't open

If the browser doesn't open during actionxm auth login, manually copy the URL and code displayed in the terminal.

Reset everything

To start fresh:

actionxm auth logout
rm -rf ~/.config/actionxm