Troubleshooting
Common issues and solutions for embedding integration
Troubleshooting
Common issues you might encounter and how to resolve them.
Token Verification Fails
Symptoms:
- Users can't authenticate
- Error messages about token verification
- Feedback form doesn't open
Solutions:
-
Verify Issuer:
- Check that
issclaim matches[Workspace Name]/[Board Title]exactly - Ensure workspace and board names haven't changed
- Check for extra spaces or special characters
- Check that
-
Check Audience:
- Verify
audclaim is exactly"roundtwo"(case-sensitive) - No extra spaces or quotes
- Verify
-
Verify Expiration:
- Check that token hasn't expired
- Ensure
expis set correctly (Unix timestamp) - Verify server time is synchronized
-
Check Public Key:
- Verify public key is correct in Round Two settings
- Ensure key includes
-----BEGIN PUBLIC KEY-----and-----END PUBLIC KEY----- - Check for formatting issues
-
Validate Token Format:
- Ensure token is a valid JWT
- Check that all required claims are present
- Verify token structure is correct
Form Doesn't Open
Symptoms:
- Clicking trigger doesn't open form
- Floating button doesn't appear
- No response when clicking custom trigger
Solutions:
-
Check Browser Console:
- Open browser developer tools
- Look for JavaScript errors
- Check network requests
-
Verify Script Loading:
- Ensure embed script is in HTML
- Check that script URL is correct
- Verify script loads without errors
-
Check Allowed Origins:
- Verify your domain is in allowed origins
- Check for typos in domain name
- Ensure protocol matches (http vs https)
-
Verify Embedding Enabled:
- Check that embedding is enabled in board settings
- Verify board is active
- Check workspace permissions
-
Test Token Endpoint:
- Manually call token endpoint
- Verify it returns a valid token
- Check for CORS issues
User Not Authenticated
Symptoms:
- Users see authentication errors
- Feedback submissions fail
- User information not displayed
Solutions:
-
Verify Token Endpoint:
- Check that endpoint is accessible
- Verify endpoint requires authentication
- Test endpoint manually
-
Check Token Claims:
- Ensure all required claims are present
- Verify
subclaim is set correctly - Check required claims (name, email) are present and valid
-
Verify Signing:
- Ensure token is signed correctly
- Check signing method matches settings
- Verify key is correct
-
Check Token Format:
- Ensure token is valid JWT
- Verify token structure
- Check for encoding issues
CORS Errors
Symptoms:
- Browser console shows CORS errors
- Requests fail with CORS messages
- Token endpoint can't be called
Solutions:
-
Check Allowed Origins:
- Verify your domain is in Round Two allowed origins
- Include protocol (https://)
- Check for trailing slashes
-
Verify CORS Headers:
- Check that Round Two API returns CORS headers
- Verify preflight requests work
- Test from different origins
-
Check Token Endpoint CORS:
- Ensure your token endpoint allows CORS
- Set appropriate CORS headers
- Allow credentials if needed
User Data Not Displaying
Symptoms:
- User names not showing
- Email not matching
- Avatars not loading
Solutions:
-
Check Token Claims:
- Verify
nameclaim is included - Check
emailclaim is present - Ensure
avatar_urlis valid
- Verify
-
Verify User Data:
- Check user data is available in your system
- Ensure data is being passed to token endpoint
- Verify data format is correct
-
Check Avatar URLs:
- Verify avatar URLs are accessible
- Check URLs use HTTPS
- Ensure images load correctly
Token Expiration Issues
Symptoms:
- Users get logged out frequently
- Tokens expire too quickly
- Form stops working after a few minutes
Solutions:
-
Check Expiration Time:
- Verify expiration is set correctly
- Ensure expiration is reasonable (5 minutes recommended)
- Check server time synchronization
-
Handle Token Refresh:
- Implement automatic token refresh
- Request new token before expiration
- Handle expiration gracefully
Rate Limiting
Symptoms:
- Requests are being blocked
- Error messages about rate limits
- Token endpoint returns 429
Solutions:
-
Check Rate Limits:
- Verify rate limits are appropriate
- Check if limits are too strict
- Monitor rate limit usage
-
Implement Backoff:
- Add exponential backoff for retries
- Handle rate limit errors gracefully
- Inform users if limits are hit
Floating Button Not Showing
Symptoms:
- Floating button doesn't appear
- Button only shows for some users
Solutions:
-
Check Authentication:
- Floating buttons only appear for authenticated users
- Verify user has a valid JWT token
- Check that token endpoint is accessible
- Ensure token verification succeeds
-
Verify Token Endpoint:
- Test token endpoint manually
- Check that endpoint returns valid token
- Verify token includes all required claims
-
Check Browser Console:
- Look for authentication errors
- Check for token verification failures
- Verify script loads correctly
Still Having Issues?
If you're still experiencing issues:
- Check the browser console for detailed error messages
- Verify all configuration matches between Round Two and your application
- Test with a simple token to isolate the issue
- Contact Round Two support with:
- Error messages
- Token structure (without sensitive data)
- Configuration details
- Steps to reproduce
Feedback
This feature is in public beta. We'd love to hear your thoughts! If you have feedback, suggestions, or encounter any issues, please contact us.