-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mitmproxy as a windows service fails to SSL #4336
Comments
May I ask why you want to run mitmproxy as a Windows service? |
I need mitmproxy to be run on Windows startup for other programs to use it and the proper way to do that in a Windows environment is by using a service. Does anything come to your mind on where the problem may be? Thanks @mhils |
My guess would have been on |
I don't think that's the problem. Check this out:
Do you know if anywhere in mitmproxy you are setting a timeout? A workaround could be not setting any |
I think we generally don't, also there would be no reason why this ony happens as a service? Do you get this with any TLS client, or just particular ones? What happens if you just run |
I'm using chrome to test this because of #4335 (comment). I made my previous code worke with:
You have a couple of places in your code where you use
|
FYI, everything in |
It's fixed in 7.0 |
Problem Description
Mitmproxy works fine if run directly but fails to intercept SSL requests when run as a windows service. I run the code as Administrator.
Steps to reproduce the behavior:
This code works fine:
But this code that uses mitmproxy within a service does not work and produces an error:
The error happens when an SSL packet gets to mitmproxy:
<< Cannot establish TLS with example.com:443 (sni: example.com): TlsException('SSL handshake error: WantReadError()')
And can be run with:
I set
confdir=r"C:\Users\username\.mitmproxy"
just in case since it runs as Administrator it is not looking for the certs in the folder where I have them but still fails.What am I missing?
Thank you in advance
System Information
The text was updated successfully, but these errors were encountered: