Skip to main content
Use this page as a decision tree when setup looks complete but traffic is still missing from Requestly Interceptor.

​
Start With The Fastest Checks

Before diving into platform-specific troubleshooting, confirm these basics:
  • Requestly Interceptor is running and the correct browser, device, or runtime is connected
  • you completed the relevant HTTP Interceptor setup guide
  • the traffic you expect is actually leaving the app or browser
  • you are looking in the correct interception view

​
Choose The Symptom That Matches Your Issue

Only HTTP Works

HTTPS traffic usually fails when the certificate is missing or not trusted.

Localhost Traffic Is Missing

Localhost and 127.0.0.1 need additional setup.

Browser Or App Is Not Showing Any Traffic

Revisit the matching browser or runtime setup path first.

Mobile Device Or Emulator Is Connected But Empty

Verify proxy, network, and certificate setup for the device or emulator.

​
Browser And System-Wide Troubleshooting

​
Only HTTP Traffic Is Intercepted

HTTPS traffic usually means the SSL certificate is not installed or trusted correctly.

​
Localhost Traffic Is Missing

Intercepting localhost or 127.0.0.1 requires extra configuration.

​
Safari-Specific Problems

Safari can require certificate regeneration and a full app restart.

​
Mobile Devices And Emulators

​
Device Is Connected But Traffic Is Missing

Check all of the following:
  • the device and desktop app are on the same network
  • the proxy settings match the Requestly Interceptor desktop app
  • the SSL certificate is installed and trusted
  • the correct setup guide was followed for the device or simulator
Use these setup references:

​
Emulator Is Not Detected

Restart the Requestly Interceptor Desktop App and reconnect the emulator. If the emulator still does not appear, re-run the matching platform setup steps.

​
Only Some Mobile Apps Are Intercepted

This is commonly caused by SSL pinning. Proxy-based tools cannot intercept pinned secure traffic unless the app supports it.

​
Other Common Causes

​
Blocked Domains

Make sure you did not exclude the target domain from interception.

​
Still Need Help?

If the issue persists, collect these details before contacting support:
  • where you are intercepting from: browser, system-wide, mobile device, emulator, terminal, or Node.js
  • operating system and Requestly Interceptor version
  • whether HTTP works while HTTPS fails
  • whether localhost traffic is involved
  • any visible proxy, certificate, or console errors