[7.12.1] ClientConnectorError: Cannot connect to host <hostname>:443 ssl:default (an existing connection was forcibly closed by the remote host)

[sentry-for-tribler]

Sentry Issue: TRIBLER-1ED

ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
  File "aiohttp\connector.py", line 986, in _wrap_create_connection
  File "asyncio\base_events.py", line 1050, in create_connection
  File "asyncio\base_events.py", line 1080, in _create_connection_transport
  File "asyncio\selector_events.py", line 846, in _read_ready__data_received

ClientConnectorError: Cannot connect to host <hostname>:443 ssl:default [an existing connection was forcibly closed by the remote host.]
(5 additional frame(s) were not displayed)
...
  File "aiohttp\connector.py", line 542, in connect
  File "aiohttp\connector.py", line 907, in _create_connection
  File "aiohttp\connector.py", line 1206, in _create_direct_connection
  File "aiohttp\connector.py", line 1175, in _create_direct_connection
  File "aiohttp\connector.py", line 992, in _wrap_create_connection

[drew2a]

Should be fixed in 7.13.0 by #7226

[sentry-for-tribler]

Also occures on 7.13.0 Sentry issue: TRIBLER-1HT

[drew2a]

It is the same error but in another place.

[drew2a]

@xoriole, it turns out that this is a completely different issue from the original one. The original issue occurred during querying the HTTP request in TorrentInfoEndpoint, and the most recent one happened "just randomly" during parameters = await request.json() in DownloadsEndpoint.

More Details

It appears that the user is conducting an experiment on their own machine (Tribler has been run with the --core argument:

sys.argv: [C:\Program Files\Tribler\tribler.exe, --core]

The error occurred here:

    async def update_download(self, request):
        infohash = unhexlify(request.match_info['infohash'])
        download = self.download_manager.get_download(infohash)
        if not download:
            return DownloadsEndpoint.return_404(request)

        parameters = await request.json() 

My guess is that the user sent the request to Tribler roughly at the same time Tribler was shutting down.

Conclusion

I propose two resolutions for the recently posted Sentry event:

1. Create a new GitHub issue.
2. Ignore it, as it appears to be a user's experiment and the number of this event is: EVENTS 2 USERS 1.

[xoriole]

@drew2a If it is possible to reproduce, I'll create an issue, otherwise, I think we can ignore it unless there are reports from more users in the future, since it seems experimental use by a single user as you pointed out.

[drew2a]

@xoriole I was not able to reproduce it.

[drew2a]

Issue closed as it was a false reopen. Although the issue appeared similar to the original in Sentry, it turned out to be a new issue. This new issue is not reproducible and seems to be the result of an experiment performed by a user.

The corresponding Sentry event has been unlinked.