#1372 - Can Not Connect - X2Go Bug report logs

X2Go Bug report logs - #1372
Can Not Connect

Date: Sun, 17 Feb 2019 19:40:01 UTC

Severity: normal

Found in version 4.1.0.3-3~bpo9+1

Received: (at submit) by bugs.x2go.org; 17 Feb 2019 19:37:03 +0000
From colony.three@protonmail.ch  Sun Feb 17 20:37:01 2019
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.7 required=3.0 tests=BAYES_50,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,SPF_HELO_PASS,
	URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id F0DE15DAF2
	for <submit@bugs.x2go.org>; Sun, 17 Feb 2019 20:37:00 +0100 (CET)
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 YVhkiUP9BWlA for <submit@bugs.x2go.org>;
	Sun, 17 Feb 2019 20:36:53 +0100 (CET)
X-Greylist: delayed 545 seconds by postgrey-1.35 at ymir.das-netzwerkteam.de; Sun, 17 Feb 2019 20:36:53 CET
Received: from mail-40133.protonmail.ch (mail-40133.protonmail.ch [185.70.40.133])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 5AEEC5DAF1
	for <submit@bugs.x2go.org>; Sun, 17 Feb 2019 20:36:53 +0100 (CET)
Date: Sun, 17 Feb 2019 19:27:45 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.ch;
	s=default; t=1550431668;
	bh=c7ZZpvx8HCnN9qM8MeK+eZuRP+RtpEL7dfIZZ0hfpGs=;
	h=Date:To:From:Reply-To:Subject:Feedback-ID:From;
	b=QO4yYXHREHG3qhajM8HKYGbQAQZ5HyFBvjkZ/n/FZSRD1oEvQBzU76e6Kvyzh84er
	 3lQuQTe6pjibGeXNqiSnZKj9L0DQrZszu97Z00CFT4juF/5oq0ry6h304hdhJcf8pR
	 IvnjsDDwsUhp741MThEoGS0UqsySrChOJmi3KP/c=
To: "submit@bugs.x2go.org" <submit@bugs.x2go.org>
From: colony.three@protonmail.ch
Reply-To: colony.three@protonmail.ch
Subject: Can Not Connect
Message-ID: <IVp5o2xC_kxKgKoMFEFiXMjcwXp8GJ0jriknmJuzHnDqXMOsN-o3fSedfw2Fw-9CW67EID-S5y3kUCsuVJgMzilcE_AW-8yafpVCLvb2a8c=@protonmail.ch>
Feedback-ID: HfZ6vTw7cEVGoeEZKQQOcJQvMMNCZ7TyUI55OCZHPJiGDHFfgEfftMiph5VbRFhfbHa5xGZDyiMvm93erb0oQw==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="b1_6354e68aed2a2ee36c701e71b522e1d6"

[Message part 1 (text/plain, inline)]

Package: x2goserver Version: 4.1.0.3-3~bpo9+1 OS Server: Armbian 5.75 4.19.20 OS Client: CentOS 7.6 4.19.7-1.el7.elrepo.x86_64 Trying to reach a headless TinkerBoard with X2Go so I can set up wifi. SELinux is disabled. I can SSH in as my user just fine, with and without -i, but when setting the Pyhoca session to "Discover SSH Keys", I get "Not a valid EC private key file!" Ok, apparently it wants an elliptic curve key. It never used to accept anything but DSA and RSA. So I made an ecdsa keypair and ssh-copy-id to the TB. Same failure. I know that X2Go can't handle ed25519 unfortunately, so I don't even have that key for my user. When setting the Pyhoca session SSH key manually to /home/bill/.ssh/id_rsa or /home/bill/.ssh/id_ecdsa, I get, "Not a valid EC private key file!" When not setting the Pyhoca session SSH key either way, and password is allowed on the TB server, it comes up with a dialog box asking for password, and when I enter the correct one I get, "Authentication failed!" Needless to say, all three methods work on the commandline. Showstopper because I can't configure wifi without NetworkManager and NetworkManager requires a GUI, and this machine is headless. Researched this to the ends of the Earth, but the issues were X2Go from a Windows client (I'm CentOS), a permissions problem on keys or .ssh, or ssh_config forwarding was disabled. None apply here.

[Message part 2 (text/html, inline)]

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Nov 21 15:34:30 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

X2Go Bug report logs - #1372 Can Not Connect

X2Go Bug report logs - #1372
Can Not Connect