# Apache 2.4 Transparent mode failure

**URL:** <https://discourse.mitmproxy.org/t/apache-2-4-transparent-mode-failure/1095>\
**Category:** help\
**Created:** [June 10, 2018, 7:49pm UTC](https://discourse.mitmproxy.org/t/apache-2-4-transparent-mode-failure/1095 "2018-06-10T19:49:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hardware\_freak](https://avatars.discourse-cdn.com/v4/letter/h/87869e/32.png) [@hardware\_freak](https://discourse.mitmproxy.org/u/hardware_freak)\
**Post date:** [June 10, 2018, 7:49pm UTC](https://discourse.mitmproxy.org/t/apache-2-4-transparent-mode-failure/1095/1 "2018-06-10T19:49:16Z")

</div>

I get the following error with the setup below:

127.0.0.1:36520: clientconnect  
127.0.0.1:36520: Transparent mode failure: OSError(92, ‘Protocol not available’)  
127.0.0.1:36520: clientdisconnect

##### Steps to reproduce the problem:

1. Debian 9 with Apache 2.4 which listens on port 80 and 433 with SSL cert and uses proxypass to reroute traffic to localhost:8080
2. mitmproxy 4 listens in transparent mode on port 8080

##### Any other comments? What have you tried so far?

When mitmproxy listens directly on these ports, no problem occurs. Do you have any hints whats going on here?

##### System information

Mitmproxy: 4.0.1  
Python: 3.6.4  
OpenSSL: OpenSSL 1.1.0h 27 Mar 2018  
Platform: Linux-4.9.0-6-amd64-x86\_64-with-debian-9.4