Connection Issues
"Subdomain not found"
Problem: Configly can't find your Zendesk instance.
Solution:
- Check your subdomain is correct (e.g.,
acmefromacme.zendesk.com) - Don't include
.zendesk.comin the subdomain field - Verify you can access Zendesk at
https://[subdomain].zendesk.com
"Authorization failed"
Problem: OAuth connection couldn't be established.
Causes:
- You cancelled the authorisation on Zendesk
- Your Zendesk account lacks admin permissions
- Network error during OAuth flow
Solution:
- Try connecting again
- Make sure to click "Allow" when Zendesk asks for permission
- Verify you're logged in as a Zendesk admin
- Check browser console for errors (F12)
"Connection test failed"
Problem: Configly can't connect to your Zendesk instance.
Solution:
- Click "Refresh Token" to get a new OAuth token
- Check Zendesk status at status.zendesk.com
- Verify your account has API access enabled
- Try disconnecting and reconnecting
Authentication errors (401/403)
Problem: You see "This looks like an authentication issue" with guidance to reconnect.
Solution:
- Your Zendesk connection may need to be reconnected
- Click the "Go to Connections" link in the error message
- Refresh your OAuth token or reconnect via OAuth
Note
Configly shows actionable guidance for authentication errors, including a direct link to your connections page.
Token Expiration
"Token expired" status
Problem: OAuth access token has expired.
Explanation: OAuth tokens expire periodically. Configly automatically refreshes them, but sometimes manual refresh is needed.
Solution:
- Click "Refresh Token" button on your connection
- This should happen automatically — if you see this often, report to support
- If refresh fails, disconnect and reconnect via OAuth
"Refresh token expired"
Problem: OAuth refresh token has expired (30 days).
Solution:
- Disconnect the connection
- Reconnect via OAuth
- You'll need to re-authorise on Zendesk
Comments
0 comments
Please sign in to leave a comment.