Error while doing SSL handshake: Unknown error

[sanjayankur31]

Hiya,

Could someone please help me connect to matrix.org (element.io)? I've followed the instructions and set up my username/password etc. However, when I try to connect, I get:

matrix: Connecting to matrix.org:443...
matrix: Doing SSL handshake...
Error while doing SSL handshake: Unknown error
matrix: disconnecting from server...

I've got a virtual enviroment set up, so all the deps should be installed correctly. I'm on Fedora 33 if that makes a difference.

weechat-2.9-2.fc33.x86_64

Cheers!

[sanjayankur31]

This is commit: 81be90c

[wavexx]

@sanjayankur31 are you using wee-slack as well by chance, or just weechat-matrix?

Did you recently got updated to python 3.9?

wee-slack/wee-slack#812

[sanjayankur31]

Ah, yes, I've also got wee-slack here, and yes, Fedora 33 is on Python 3.9 too. So, it's probably the same issue.

[jonorthwash]

Same issue, I recently upgraded to python3.9 and I'm using wee-slack as well.

[demlak]

is there any chance of getting this fixed?
i'm not on wee-slack.

Edit: a /script reload matrix.py seems to help..

[wavexx]

@demlak are you using other python plugins, or just weechat-matrix?

[demlak]

i'm using autosort.py, buffer_autohide.py, matrix.py, shell.py, weemustfeed.py, whois_on_query.py

[wavexx]

Given the problem, I suspect that if you only use "matrix.py" the problem will go away (just to verify, I know this is not a solution).

[demlak]

i gave it a try.. if i start without weemustfeed.py, the error does not happen.. when i load weemustfeed.py manualy after matrix.py has connected to server.. the connection fails and the error starts again

[wavexx]

I suppose weemustfeed is doing some connection underneath. As expected, this is similar to wee-slack.

[Zenuncl]

Having similar issue, don't have wee-slack or weemustfeed but I do have another jabber.py running.
Python 3.9
Any plan to fix it soon?

[sanjayankur31]

@wavexx : not a python pro either, but I can try to help with this. Any hints on getting started?

@SharkIng : if you can help diagnose the issue, that'll be helpful. @wavexx has already noted that this isn't an easy one to diagnose. (See also: wee-slack/wee-slack#812)

[poljar]

The error happens here. Adding a `print(error) reveals this error message:

21:39 python: stdout/stderr (matrix): The operation did not complete (read) (_ssl.c:1123)

I have no idea why that would start happening, seems like the other scripts start messing with the existing SSLContext. If a /script reload matrix or loading the matrix script last helps I'm inclined to leave this be and continue working on the rewrite.

[poljar]

There's this comment on the Python bug tracker pointing in the same direction as well:

tl;dr SSLObject and SSLSocket cannot be safely used by multiple threads at the same time. SSLContext can be shared across multiple threads. However it's not safe to reconfigure a context once it's attached to a connection. Only getters, wrap_*(), and load_verify_locations() are safe.

[fluix-dev]

Just throwing more logs here, after running /script reload matrix, wee-slack spits out the same error as print(error) would:

python: error in function "receive_ws_callback"
python: stdout/stderr (slack): Traceback (most recent call last):
python: stdout/stderr (slack):   File "/home/main/.config/weechat/python/autoload/wee_slack.py", line 162, in wrapper
python: stdout/stderr (slack):     return f(*decode_from_utf8(args), **decode_from_utf8(kwargs))
python: stdout/stderr (slack):   File "/home/main/.config/weechat/python/autoload/wee_slack.py", line 531, in receive_ws_callback
python: stdout/stderr (slack):     handle_socket_error(e, team, 'receive')
python: stdout/stderr (slack):   File "/home/main/.config/weechat/python/autoload/wee_slack.py", line 526, in receive_ws_callback
python: stdout/stderr (slack):     opcode, data = team.ws.recv_data(control_frame=True)
python: stdout/stderr (slack):   File "/usr/lib/python3.9/site-packages/websocket/_core.py", line 331, in recv_data
python: stdout/stderr (slack):     opcode, frame = self.recv_data_frame(control_frame)
python: stdout/stderr (slack):   File "/usr/lib/python3.9/site-packages/websocket/_core.py", line 344, in recv_data_frame
python: stdout/stderr (slack):     frame = self.recv_frame()
python: stdout/stderr (slack):   File "/usr/lib/python3.9/site-packages/websocket/_core.py", line 378, in recv_frame
python: stdout/stderr (slack):     return self.frame_buffer.recv_frame()
python: stdout/stderr (slack):   File "/usr/lib/python3.9/site-packages/websocket/_abnf.py", line 361, in recv_frame
python: stdout/stderr (slack):     self.recv_header()
python: stdout/stderr (slack):   File "/usr/lib/python3.9/site-packages/websocket/_abnf.py", line 309, in recv_header
python: stdout/stderr (slack):     header = self.recv_strict(2)
python: stdout/stderr (slack):   File "/usr/lib/python3.9/site-packages/websocket/_abnf.py", line 396, in recv_strict
python: stdout/stderr (slack):     bytes_ = self.recv(min(16384, shortage))
python: stdout/stderr (slack):   File "/usr/lib/python3.9/site-packages/websocket/_core.py", line 453, in _recv
python: stdout/stderr (slack):     return recv(self.sock, bufsize)
python: stdout/stderr (slack):   File "/usr/lib/python3.9/site-packages/websocket/_socket.py", line 100, in recv
python: stdout/stderr (slack):     bytes_ = sock.recv(bufsize)
python: stdout/stderr (slack):   File "/usr/lib/python3.9/ssl.py", line 1226, in recv
python: stdout/stderr (slack):     return self.read(buflen)
python: stdout/stderr (slack):   File "/usr/lib/python3.9/ssl.py", line 1101, in read
python: stdout/stderr (slack):     return self._sslobj.read(len)
python: stdout/stderr (slack): ssl.SSLWantReadError: The operation did not complete (read) (_ssl.c:2622)