# Mitmproxy/dump/web not fowarding upstream traffic to burp

**URL:** <https://discourse.mitmproxy.org/t/mitmproxy-dump-web-not-fowarding-upstream-traffic-to-burp/1004>\
**Category:** Uncategorized\
**Created:** [April 24, 2018, 3:24pm UTC](https://discourse.mitmproxy.org/t/mitmproxy-dump-web-not-fowarding-upstream-traffic-to-burp/1004 "2018-04-24T15:24:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![diis](https://avatars.discourse-cdn.com/v4/letter/d/bcef8e/32.png) [@diis](https://discourse.mitmproxy.org/u/diis)\
**Post date:** [April 24, 2018, 3:24pm UTC](https://discourse.mitmproxy.org/t/mitmproxy-dump-web-not-fowarding-upstream-traffic-to-burp/1004/1 "2018-04-24T15:24:51Z")

</div>

Hello all, I’m having massive problems trying to create an upstream proxy to Burp. I have the following set up:

1. Latest mitmproxy download (3.0.4) and latest Burp Pro (1.7.33) download.
2. Both mitmproxy and Burp certificates installed to use SSL.
3. Burp settings:

- Listening on all interfaces on port 8080
- Invisible proxying enabled
- Intercept Server Responses: Or|Request| was Intercepted

1. Firefox set to listen on **Port 9090**

I then run the command:  
`mitmdump --listen-port 9090 --upstream="http://My_Ip_Addr:8080"`

I can hit HTTPS sites, but no matter what I do the requests don’t show up in my burp log. I also tried disabling SSL certificate checks using the `--set insecure_ssl=true` option.

I think this is a problem with MITM as when I change my proxy in Firefox to use port 8080 requests show up as normal. Any advice?

---

<div class="post-metadata">

**Author:** ![mhils](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.mitmproxy.org/mhils/32/7_2.png) [@mhils](https://discourse.mitmproxy.org/u/mhils)\
**Post date:** [April 25, 2018, 2:18pm UTC](https://discourse.mitmproxy.org/t/mitmproxy-dump-web-not-fowarding-upstream-traffic-to-burp/1004/2 "2018-04-25T14:18:44Z")

</div>

Hi,

There’s no `--upstream` option in mitmproxy. You want `--mode upstream:localhost:8080`.

---

<div class="post-metadata">

**Author:** ![diis](https://avatars.discourse-cdn.com/v4/letter/d/bcef8e/32.png) [@diis](https://discourse.mitmproxy.org/u/diis)\
**Post date:** [April 25, 2018, 2:45pm UTC](https://discourse.mitmproxy.org/t/mitmproxy-dump-web-not-fowarding-upstream-traffic-to-burp/1004/3 "2018-04-25T14:45:41Z")

</div>

OMG you are a legend!!! I was trying to troubleshoot this forever. I’m getting 502 bad gateway errors due to certificate validation problems. Do I always have to specify `--set insecure_ssl=true` or is there a way around that?

---

<div class="post-metadata">

**Author:** ![mhils](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.mitmproxy.org/mhils/32/7_2.png) [@mhils](https://discourse.mitmproxy.org/u/mhils)\
**Post date:** [April 25, 2018, 7:29pm UTC](https://discourse.mitmproxy.org/t/mitmproxy-dump-web-not-fowarding-upstream-traffic-to-burp/1004/4 "2018-04-25T19:29:21Z")

</div>

You can also specify it in [`~/.mitmproxy/config.yaml`](https://docs.mitmproxy.org/stable/concepts-options/) or set the ssl\_verify\_upstream\_trusted\_ca option. 🙂