> For the complete documentation index, see [llms.txt](https://docs.proxyman.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proxyman.com/troubleshooting/i-couldnt-see-any-traffics-on-proxyman.md).

# I couldn't see any traffics on Proxyman

### 1. Problems

* After launching the app, the request list is empty
* There are no requests captured by Proxyman?
* I don't see any requests on the app
* I can see some request on my Mac, but no request on my remote devices (iOS, Android)

{% hint style="info" %}
For remote devices (iOS or Android), please check out this [troubleshoot](/troubleshooting/my-ios-devices-couldnt-connect-to-proxyman-via-proxy.md).
{% endhint %}

![](/files/-M5oNlGIE51483XhMSa4)

### 2. Solution

### 2.1 Turn OFF all VPN apps on your Mac machine

Some VPN apps accidentally revert the HTTP Proxy in Network as soon as Proxyman overrides it. As a result, HTTP Traffic won't go through Proxyman port at 9090.

Close all VPN app if possible and relaunch Proxyman

### 2.2. Double-check HTTP Proxy in Network

Proxyman would override or revert the HTTP Proxy at the launch time or exit, but some apps could revert back.

Let open System Preference -> Network -> Wifi -> Proxies tab:

* Check the **Web Proxy (HTTP)** and **Secure Web Proxy (HTTPS)**
* Make sure the port is the same as the Proxyman port
* IP is **127.0.0.1**

Save and check the requests on Proxyman

![](/files/-M5oPPHJI6eMwhUjoubn)

### 2.3 Install Proxyman Helper Tool

By default, Proxyman attempts to override the system HTTP Proxy by using `networksetup` CLI, but it might be failed in certain scenarios.

\=> Let's try to install Proxyman Helper Tool. This tool will override the system HTTP Proxy properly. Please open Proxyman Preference -> Advanced Tab -> Install Helper Tool

![](/files/-MJPPWnJw44Jz-e57Mqi)

### 2.4 Some HTTP/HTTPS Requests are missing from Proxyman

Alamofire or URLSession might use the cached response for your request. As a result, the actual request doesn't hit the server. Thus, Proxyman could not capture and display it on the app.

Solution:

* Disable the cache mechanism on URLSession or Alamofire.
* Use the [No Caching Tool](/advanced-features/no-caching.md) (⌥⌘N)