session-pysogs icon indicating copy to clipboard operation
session-pysogs copied to clipboard

Failed to decrypt onion request: Could not finalise decryption

Open vsatmydynipnet opened this issue 2 years ago • 3 comments

I have masses of

Feb 17 12:00:46 sogs uwsgi[4376]: #033[32m2023-02-17 12:00:46,399#033[0m #033[35msogs#033[0m #033[34msogs.web[4376]#033[0m #033[1;30mWARNING#033[0m #033[33mFailed to decrypt onion request: Could not finalise decryption#033[0m

entries in the syslog.

Is this ok, or is there something running wrong?

Running standalone on Debian Bullseye fresh setup, VM is only running sogs, nothing else on this VM.

vsatmydynipnet avatar Feb 17 '23 11:02 vsatmydynipnet

I have the same issue.

Failed to decrypt onion request: Could not finalise decryption
/oxen/v4/lsrpc => generated 192 bytes in 2 msecs (HTTP/1.1 400) 2 headers in 89 bytes (2 switches on core 0)

I noticed this while checking as someone said one of my rooms was down.

zcyph avatar Mar 21 '23 12:03 zcyph

did your sogs change the public key it uses?

majestrate avatar Mar 21 '23 22:03 majestrate

@majestrate it did not

for clarity, this turned out to be an issue between a specific user and the sogs, not a sogs wide issue

others were able to use the room when that user could not and that user was eventually able to later reconnect

zcyph avatar Mar 21 '23 22:03 zcyph