[X2Go-User] The remote NX proxy closed the connection ... PANIC ... stage 7

William Oquendo woquendo at gmail.com
Mon Nov 25 20:12:47 CET 2024


Hi.
I need help with the error:

Loop: PANIC! The remote NX proxy closed the connection.
Error: The remote NX proxy closed the connection.
Loop: PANIC! Failure negotiating the session in stage '7'.
Error: Failure negotiating the session in stage '7'.
Loop: PANIC! Wrong version or invalid session authentication cookie.
Error: Wrong version or invalid session authentication cookie.
Session: Terminating session at 'Fri Nov 22 21:49:10 2024'.

This started after an update in my base os (slackware current). I just
recompiled x2go, nx-libs and the perl deps. And now I cannot connect,
getting always this error message.

I have read too many block post, mailing list messages (from this list,
with similar title), and so on, with the same keywords, and nothing works.
Some post are very old, like from 10 years ago, and yet I tried what was
suggested. Looking for info in the web is now almost hopeless, all the
links that appear are marked as already visited by me. Some LLM suggest
basically the same thing (plus deleting ~/.x2go and things like that, and
gues, do not work). I have tried changing nx-libs versions, x2goserver
versions, deleting and recreating the data base, etc. Both ssh and ssh -X
work. I really don't have a clue. Normally when x2go failed I just had to
recompile perl-DBD... but this is a very different problem. I suspect is
something related with permission with some magic cookie, but nothing
appears in the logs that give some clue.

I have played also with x2gstartagent and it fails with errors showing that
/usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper insertsession 50
sala29.salafis.net myuser-50-1732504908
failed, but I was not able to make it run or understand the problem, and
sometimes it seems that this happens because I ran it remotely, using ssh,
so no DISPLAY var was set.

I really need some tip, gidance, help. Thanks in advance

This is important because is the tool we use to access remotely a coputer
room, so right now students cannnot use it and are relying on workarounds
like accessing file using vscode remote-desktop extension, or a complicated
reverse tunnel with turbovnc, and so on.

INSTALLED VERSIONS
/var/log/packages/nx-libs-3.5.99.27-x86_64-1_SBo (tested also older
versions)
/var/log/packages/perl-5.40.0-x86_64-2
/var/log/packages/perl-Capture-Tiny-0.48-x86_64-1_SBo
/var/log/packages/perl-Config-Simple-4.58-x86_64-1_SBo
/var/log/packages/perl-DBD-SQLite-1.76-x86_64-1_SBo
/var/log/packages/perl-File-ReadBackwards-1.05-x86_64-1_SBo
/var/log/packages/perl-File-Which-1.27-x86_64-1_SBo
/var/log/packages/perl-IPC-System-Simple-1.30-noarch-1_SBo
/var/log/packages/perl-Module-Build-0.4234-noarch-1_SBo
/var/log/packages/perl-Switch-2.17-x86_64-1_SBo
/var/log/packages/perl-Switch-2.17-x86_64-1_SBo-upgraded-2024-11-24,18:03:28
/var/log/packages/perl-Try-Tiny-0.28-x86_64-1_SBo
/var/log/packages/perl-Unix-Syslog-1.1-x86_64-1_SBo
/var/log/packages/perl-file-basedir-0.09-x86_64-1_SBo
/var/log/packages/x2goserver-4.1.0.4-x86_64-1_SBo (I tested even with te
latest 4.1.0.6)



-- 

Best regards / Cordialmente,

William-Fernando Oquendo
--------------------------
Este correo puede carecer de tildes o eñes debido al teclado.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.x2go.org/pipermail/x2go-user/attachments/20241125/2b5534f8/attachment.htm>


More information about the x2go-user mailing list