Troubleshooting
Common issues and how to fix them.
Rules Not Matching Requests
Problem: You added a rule but donât see request counts increasing.
Solutions:
- Check your pattern - Use
*domain.cominstead of*.domain.comif targeting the base domain - Ensure the rule is enabled - Toggle should be ON in the rules list
- Ensure extension is enabled - Toggle at the top should be ON
- Check Service Worker logs:
- Go to
chrome://extensions - Click âService Workerâ under Auth HI!
- Navigate to your target site
- Look for
[Request Tracker]logs
- Go to
- Verify the site makes API calls - Some sites use GraphQL, WebSockets, or no external calls
Extension Not Injecting Headers
Problem: Rules show as active but headers arenât being sent.
Solutions:
- Check for errors - Go to
chrome://extensionsand look for error messages - Verify pattern syntax - Test with
*://domain.com/*for explicit matching - Check token format - Should be just the token, NOT
Bearer {token} - Inspect Network tab:
- Open DevTools â Network
- Find a matching request
- Check Request Headers for
Authorization
- Some sites block extension headers - Rare, but possible with strict CSP
Service Worker Crashes
Problem: Extension stops working after a while.
Why this happens:
- Chrome kills idle service workers after ~30 seconds (normal behavior)
- Extension auto-restarts on next event (opening panel, new request)
Solutions:
- This is usually normal - Service workers are designed to sleep
- Check for errors in Service Worker console if persistent
- Reload extension - Go to
chrome://extensionsand click reload icon - Update Chrome - Make sure youâre on the latest version
Side Panel Wonât Open
Problem: Clicking extension icon doesnât open the side panel.
Solutions:
- Check Chrome version - Side panel requires Chrome 114+
- Reload the extension - Go to
chrome://extensionsand reload - Check for errors - Look for error badge on extension icon
- Reinstall - Remove and reinstall the extension
Request Counts Not Updating
Problem: Rules show active but counts stay at 0.
Solutions:
- Refresh the side panel - Close and reopen it
- Check restricted pages - Extensions canât track on
chrome://orchrome-extension://pages - Verify webRequest permission - Should be enabled (check manifest)
Pattern Validation Errors
Problem: Canât save a rule due to validation error.
Common causes:
- Empty pattern
- Empty token
- Invalid characters in pattern
- Duplicate pattern (already exists)
Solutions:
- Use simple patterns first:
domain.comor*.domain.com - Avoid special characters except
*,.,/,:,- - Check for duplicate rules with same pattern
Still Having Issues?
- Report a bug on GitHub
- Ask a question in Discussions
- Check the READMEÂ for additional documentation
Last updated on