nfx
Empty reply from server
root@sayrix1:~# curl -D - -x http://127.0.0.1:8090 -k http://httpbin.org/get
curl: (52) Empty reply from server
root@sayrix1:~#
@Sayrix can you check the debug output from slrp process, what do you see there?
@nfx I too encountered this when I used http and not https, not sure why and I didn't dive into this (as of now)
For now running the whole thing w/ https works around (even if there's no real certificate chain)
@Sayrix can you check the debug output from slrp process, what do you see there?
I will try right now
Yup me too, i can't connect in http but in https it connect but the proxy don't works because it says MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT
And in the console: 2024/02/25 17:23:33 http: TLS handshake error from 127.0.0.1:49468: remote error: tls: bad certificate
I think that to fix it is to make the mitm in http or socks to prevent ssl error
I think that to fix it is to make the mitm in http or socks to prevent ssl error
yea you just have to cancel SSL check on everything...which is not good :~(
yea you just have to cancel SSL check on everything...which is not good :~(
Firefox don't let me to cancel it