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.
Hi,
I have no clue what's going on at your end, too many variables. I am not even sure on what side you updated/recompiled everthing.
Nevertheless you can try to cut the problem down a bit: the ones back from the server to the client side
- disable filesharing, audio, printing in the session configuration. This way x2goclient will have to organize less connections, especially
- try to connect using pyhoca client. If it works we know the server side is ok tne the problem is with x2goclient
- try to use the official binaries, maybe even on a test machine with another OS. This can also used to isolate the problem (server/client side)
- run x2goclient in debug mode to get some more logs
- you should really check if the database is the problem. From https://wiki.x2go.org/doku.php/wiki:advanced:x2goserver-in-detail is looks liek it is essential that this step works.Maybe re-create it? There is a service that regularly drop ophan session entries. You can also run this manually, is called x2gocleansessions. And there's x2godbadmin.
Uli
On Mon, Nov 25, 2024 at 8:13 PM William Oquendo <woquendo@gmail.com> wrote:
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.
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
-
Ulrich Sibiller -
William Oquendo