X2Go Bug report logs - #1215
Bug: "The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication credentials passed to the server."

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#1215: Bug: "The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication credentials passed to the server."
Reply-To: dood0240skpw33@toothandmail.com, 1215@bugs.x2go.org
Resent-From: dood0240skpw33@toothandmail.com
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Sun, 24 Sep 2017 19:50:01 +0000
Resent-Message-ID: <handler.1215.B.15062824874456@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: report 1215
X-X2Go-PR-Package: x2goserver
X-X2Go-PR-Keywords: 
Received: via spool by submit@bugs.x2go.org id=B.15062824874456
          (code B); Sun, 24 Sep 2017 19:50:01 +0000
Received: (at submit) by bugs.x2go.org; 24 Sep 2017 19:48:07 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=3.0 tests=BAYES_50,FREEMAIL_FROM,
	LOTS_OF_MONEY,SPF_HELO_PASS autolearn=ham autolearn_force=no version=3.4.1
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id ECA845DACF
	for <submit@bugs.x2go.org>; Sun, 24 Sep 2017 21:48:01 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de
Received: from ymir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ciZ4Ums7IIfY for <submit@bugs.x2go.org>;
	Sun, 24 Sep 2017 21:47:57 +0200 (CEST)
X-Greylist: delayed 401 seconds by postgrey-1.35 at ymir.das-netzwerkteam.de; Sun, 24 Sep 2017 21:47:56 CEST
Received: from vfemail.net (onethreetwo.vfemail.net [199.16.11.132])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 9668F5DA81
	for <submit@bugs.x2go.org>; Sun, 24 Sep 2017 21:47:56 +0200 (CEST)
Received: (qmail 59723 invoked by uid 89); 24 Sep 2017 19:41:13 -0000
Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1)
  by localhost with (DHE-RSA-AES256-SHA encrypted) SMTP; 24 Sep 2017 19:41:13 -0000
Received: (qmail 59666 invoked by uid 89); 24 Sep 2017 19:40:55 -0000
Received: by simscan 1.4.0 ppid: 59664, pid: 59665, t: 0.0020s
         scanners:none
Received: from unknown (HELO smtp102-2.vfemail.net) (172.16.100.62)
  by FreeQueue with SMTP; 24 Sep 2017 19:40:55 -0000
Received: (qmail 1799 invoked by uid 89); 24 Sep 2017 19:40:55 -0000
Received: by simscan 1.4.0 ppid: 1793, pid: 1796, t: 0.0725s
         scanners:none
Received: from unknown (HELO localhost) (ZG9vZDAyNDBza3B3MzNAdG9vdGhhbmRtYWlsLmNvbQ==@172.16.100.93)
  by 172.16.100.62 with ESMTPA; 24 Sep 2017 19:40:55 -0000
Date: Sun, 24 Sep 2017 19:40:55 +0000
Message-ID: <20170924194055.Horde.8NYXpqD9NIae-YDxSme1hxT@www.vfemail.net>
From: dood0240skpw33@toothandmail.com
To: submit@bugs.x2go.org
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline

Package: x2goserver

Version: 4.0.1.20

I guess it's the x2goserver package that has the bug?? I don't know  
about what package precisely!...

***How to Reproduce the bug:***

Install, following the correct and proper instructions, the x2goclient  
and the x2goserver on respectively your client and your server.
(My client is Kali Linux 2017 latest version)
(My server is a Raspberry Pi Version 3)

Once the server packages are correctly installed in the server, and  
once the client package(s) is correctly installed in the client:
open your x2go client by issuing "x2goclient" in your terminal (my  
client terminal is root, so I actually issue the command to open the  
client as root, but I don't get any kind of problem)

create a new session with the correct details, and select LXDE  
protocol. (My rpi3 has lxde package installed and correctly working)
Keep in mind the rpi is booted on the cli environment, that's why I'm  
using the LXDE protocol.

Ok then start the connection (after insterting the proper password)
Status "connecting" will show up in the x2go client.
wait a few minutes and a window from the x2go client will pop up saying:
"The remote proxy closed the connection while negotiating
the session. This may be due to the wrong authentication
credentials passed to the server."


Looking at the logs at /var/log/syslog on the x2go server, the output is:
root@myrpithree:~# tail -f /var/log/syslog | grep x2go
Sep 24 14:11:56 myrpithree /usr/sbin/x2gocleansessions[3591]:  
myrpithree-50-1506280314_stDLXDE_dp24: state file for this session  
does not exist:  
/tmp/.x2go-myrpithree/C-myrpithree-50-1506280314_stDLXDE_dp24/state  
(this can be ignored during session startups)
Sep 24 14:12:00 myrpithree /usr/sbin/x2gocleansessions[3591]:  
myrpithree-50-1506280314_stDLXDE_dp24: state file for this session  
does not exist:  
/tmp/.x2go-myrpithree/C-myrpithree-50-1506280314_stDLXDE_dp24/state  
(this can be ignored during session startups)
Sep 24 14:12:03 myrpithree /usr/sbin/x2gocleansessions[3591]:  
myrpithree-50-1506280314_stDLXDE_dp24: state file for this session  
does not exist:  
/tmp/.x2go-myrpithree/C-myrpithree-50-1506280314_stDLXDE_dp24/state  
(this can be ignored during session startups)
Sep 24 14:12:40 myrpithree /usr/bin/x2gostartagent: successfully  
started X2Go agent session with ID myrpithree-50-1506280314_stDLXDE_dp24
^C

The session has been successfully started, however I still get that  
boring message and thus I do not get the RDP window!

I've see this bug is around for quite some years, ANY TEMPORARY  
SOLUTION PLEASE?

DO YOU WANT ME TO POST MORE OUTPUTS OR SOMETHING? PLEASE LET ME KNOW.


-------------------------------------------------

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  

Send a report that this bug log contains spam.