also fixing
Code:Invalid compressed gzip data
Printable View
found this error at terminal , maybe useful for next fixer update .
something elseCode:127.0.0.1:60177: clientconnect
127.0.0.1:60177: Traceback (most recent call last):
File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "mitmproxy\proxy\server.py", line 121, in handle
File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
File "mitmproxy\proxy\protocol\tls.py", line 245, in __call__
File "mitmproxy\net\tls.py", line 468, in from_file
File "mitmproxy\net\tls.py", line 401, in get_client_hello
File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)
Traceback (most recent call last):
File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "mitmproxy\proxy\server.py", line 121, in handle
File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
File "mitmproxy\proxy\protocol\tls.py", line 245, in __call__
File "mitmproxy\net\tls.py", line 468, in from_file
File "mitmproxy\net\tls.py", line 401, in get_client_hello
File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)
mitmproxy has crashed!
Please lodge a bug report at: https://github.com/mitmproxy/mitmproxy
127.0.0.1:60177: clientdisconnect
127.0.0.1:60186: clientconnect
anonCode:127.0.0.1:55332: clientdisconnect
127.0.0.1:55334: clientconnect
127.0.0.1:55334: Traceback (most recent call last):
File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "mitmproxy\proxy\server.py", line 121, in handle
File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
File "mitmproxy\proxy\protocol\tls.py", line 281, in __call__
File "mitmproxy\proxy\protocol\tls.py", line 386, in _establish_tls_with_client
File "mitmproxy\connections.py", line 139, in convert_to_tls
File "mitmproxy\net\tls.py", line 468, in from_file
File "mitmproxy\net\tls.py", line 401, in get_client_hello
File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)
Traceback (most recent call last):
File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "mitmproxy\proxy\server.py", line 121, in handle
File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
File "mitmproxy\proxy\protocol\tls.py", line 281, in __call__
File "mitmproxy\proxy\protocol\tls.py", line 386, in _establish_tls_with_client
File "mitmproxy\connections.py", line 139, in convert_to_tls
File "mitmproxy\net\tls.py", line 468, in from_file
File "mitmproxy\net\tls.py", line 401, in get_client_hello
File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)
mitmproxy has crashed!
Please lodge a bug report at: https://github.com/mitmproxy/mitmproxy
127.0.0.1:55334: clientdisconnect
can you update it to the last versions ?
since this one from but the last mitmproxy is Nov 2, 2022 , off-course when you got some free time .
Well, that's bad :smilie4: If you can isolate one or more .torrent files that trigger these errors consistently, I'd be very interested to see them!
The mitmproxy in v7 already wasn't current at the time of release, but I had to do that to maintain Windows 7 compatibility and avoid a memory leak in the then-latest version.Quote:
the last mitmproxy is Nov 2, 2022
With that said, there's a possibility of updating the project to v8... stay tuned!
i don't know which one cause the crash but am watching ,
i can send you list of those trackers using fixer7 .
:top:
anon
can you add something at the .bat to show the time ?
i searched and found this but don't know which one and where ?
by the way the crash happen again .
i think found one of four crashes :
The handshake failed due to an unexpected packet format.
Retrying in 30s.
sent you another torrent from the same tracker (untouched) at PM .
Error messages come from the mitmproxy process, but if you replace the contents of fixer.py with this, you can add a basic yet effective logging feature.
No need to restart Fixer as the change applies immediately.Code:https://paste.ggc-project.de/?018459a5dfbe3231#EM14EAKCYquSCvcUU7rbXX3gAuiPP5G8a2nMaJnndBpR
Thanks, this one has happened before but it is very hard to reproduce, so I never found what causes it or if it's something I can fix at all.
I found a way to upgrade mitmproxy without dropping Windows 7 support, so I'm hoping switching to the latest version will finally end weird bugs like these (there were major changes in the engine since 4.0.4).
now its show the time and the tracker , perfect :top: ,thanks
:top:Quote:
Thanks, this one has happened before but it is very hard to reproduce, so I never found what causes it or if it's something I can fix at all.
I found a way to upgrade mitmproxy without dropping Windows 7 support, so I'm hoping switching to the latest version will finally end weird bugs like these (there were major changes in the engine since 4.0.4).
i found the others two trackers if you still interested .
another errors :
Quote:
127.0.0.1:61158: Client Handshake failed. The client may not trust the proxy's certificate for bwtorrents.tv.
Quote:
127.0.0.1:60544: SOCKS5 mode failure: TcpDisconnect('[WinError 10054] An existing connection was forcibly closed by the remote host',)
Okay, I checked everything you sent me.
- Connection was forcibly closed: haven't managed to replicate this so far. The message merely means the TCP connection was reset on the server side and there are many possible reasons for that.
- mitmproxy has crashed: your logs indicate it is caused by the above error, which normally shouldn't be fatal...
- Unexpected packet format: haven't managed to replicate this one either. This error means the tracker is not returning a valid response to the initial TLS Client Hello packet. The best I can do is capturing traffic in hopes of eventually encountering it, then check what exactly is being sent (and I'm doing that right now).
- Client handshake failed: as per https://www.sb-innovation.de/showthread.php?p=360275 this may be caused by or be interconnected to the others.
None of the trackers you sent me have any bad certificates or TLS misconfigurations. The best I can do while I continue running tests is giving you a second update to fixer.py; this one strips some more long HTTP headers, and if the crashes still occur, the extra logging will tell us whether it's before or after processing the response.
Code:https://paste.ggc-project.de/?d5d87f686c008867#6GBedd5JzVsUfi6coob9YTutxohQJCrsTg3y6omYf7WD
Code:[2023-05-01 15:34:51.927766] Making https connection to bwtorrents.tv:443
127.0.0.1:53897: clientconnect
127.0.0.1:53897: Traceback (most recent call last):
File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "mitmproxy\proxy\server.py", line 121, in handle
File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
File "mitmproxy\proxy\protocol\tls.py", line 281, in __call__
File "mitmproxy\proxy\protocol\tls.py", line 386, in _establish_tls_with_client
File "mitmproxy\connections.py", line 139, in convert_to_tls
File "mitmproxy\net\tls.py", line 468, in from_file
File "mitmproxy\net\tls.py", line 401, in get_client_hello
File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)
Traceback (most recent call last):
File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "mitmproxy\proxy\server.py", line 121, in handle
File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
File "mitmproxy\proxy\protocol\tls.py", line 281, in __call__
File "mitmproxy\proxy\protocol\tls.py", line 386, in _establish_tls_with_client
File "mitmproxy\connections.py", line 139, in convert_to_tls
File "mitmproxy\net\tls.py", line 468, in from_file
File "mitmproxy\net\tls.py", line 401, in get_client_hello
File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)
mitmproxy has crashed!
Please lodge a bug report at: https://github.com/mitmproxy/mitmproxy
127.0.0.1:53897: clientdisconnect
127.0.0.1:53898: clientconnect
[2023-05-01 15:34:54.873724] Making https connection to bwtorrents.tv:443
Code:127.0.0.1:57160: clientconnect
[2023-05-01 18:24:24.433874] Making https connection to digitalcore.club:443
[2023-05-01 18:24:25.253397] Processing response from digitalcore.club:443 as https
127.0.0.1:57160: clientdisconnect
127.0.0.1:57220: clientconnect
Traceback (most recent call last):
File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "mitmproxy\proxy\server.py", line 121, in handle
File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
File "mitmproxy\proxy\protocol\tls.py", line 245, in __call__
File "mitmproxy\net\tls.py", line 468, in from_file
File "mitmproxy\net\tls.py", line 401, in get_client_hello
File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)
127.0.0.1:57220: Traceback (most recent call last):
File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "mitmproxy\proxy\server.py", line 121, in handle
File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
File "mitmproxy\proxy\protocol\tls.py", line 245, in __call__
File "mitmproxy\net\tls.py", line 468, in from_file
File "mitmproxy\net\tls.py", line 401, in get_client_hello
File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)
mitmproxy has crashed!
Please lodge a bug report at: https://github.com/mitmproxy/mitmproxy
127.0.0.1:57220: clientdisconnect
127.0.0.1:57221: clientconnect
[2023-05-01 18:27:48.711760] Making https connection to torrentland.li:443
[2023-05-01 18:27:49.492994] Processing response from torrentland.li:443 as https
[2023-05-01 18:27:49.492994] Killing HTTP header "X-RateLimit-Limit" in response
[2023-05-01 18:27:49.492994] Killing HTTP header "X-RateLimit-Remaining" in response
[2023-05-01 18:27:49.492994] Killing HTTP header "Permissions-Policy" in response
127.0.0.1:57221: clientdisconnect
Those logs show the connection is reset before receiving a response. So it's either something at the network level, or the tracker doesn't like the request and immediately sends a RST (but that's unlikely since all we do is parse the Host header and change the TCP destination port if required)
Since I haven't managed to encounter any of these so far, I don't have any other ideas for now :gnoes: I think I'll focus on upgrading to mitmproxy 9, and if the problems continue, make a special debug build to get more data.
using mRatio without fixer. Can i start using fixer and continue with the existing seeding list in mRatio?
Update: Got it from tutorial.