Hi Mike:

Thanks for the help...no joy yet, but some updates (in a separate email, I'd like to circle back around on using SSL/SSH and the option of using x2goplugin with SSL as an alternative short term):

1. I mis-wrote earlier - the server I'm using is Wheezy, and the client Squeeze. Not sure that matters, but wanted to convey as such.

2. FYI, can go to server's webpage and get generic apache "It works! This is the default web page for this server. The web server software is running but no content has been added, yet.", so think apache is running. SSH is running as well on the server.

3. Again FYI have been trying x2gobroker-wsgi (not x2gobroker-daemon)

4. When I try: x2goclient --broker-url=http://xxx.xxx.xxx.xxx/plain/inifile

I get an error window: Login Failed! Please try again

When I try:

x2goclient --broker-url="ssh://xxx.xxx.xxx.xxx/usr/bin/x2gobroker --backend=inifile"

I get: sh: 1: /usr/bin/x2gobroker: not found

FYI: on the server, there isn't an x2gobroker in /usr/bin....there is an x2gobroker script in /usr/sbin.

If I try: x2goclient --broker-url="ssh://xxx.xxx.xxx.xxx/usr/sbin/x2gobroker --backend=inifile"

I get an error window with a fair amount of info: 2013-10-29 19:01:05,325 - broker - INFO - X2Go Session Broker (0.0.2.3), written by Mike Gabriel (X2Go Project) <mike.gabriel@das-netzwerkteam.de> 2013-10-29 19:01:05,325 - broker - INFO - Setting up the broker's environment... 2013-10-29 19:01:05,325 - broker - INFO - X2GOBROKER_DEBUG: True 2013-10-29 19:01:05,326 - broker - INFO - X2GOBROKER_CONFIG: /etc/x2go/x2gobroker.conf 2013-10-29 19:01:05,326 - broker - INFO - X2GOBROKER_AGENT_CMD: /usr/lib/x2go/x2gobroker-agent 2013-10-29 19:01:05,326 - broker - INFO -
X2GOBROKER_AUTHSERVICE_SOCKET: /run/x2gobroker/x2gobroker-authservice.socket 2013-10-29 19:01:05,326 - broker - INFO - X2GOBROKER_DEFAULT_BACKEND: zeroconf 2013-10-29 19:01:05,326 - broker - INFO - X2GOBROKER_SSL_CERTFILE: 2013-10-29 19:01:05,326 - broker - INFO - X2GOBROKER_SSL_KEYFILE: 2013-10-29 19:01:05,327 - broker - WARNING - X2Go Session Broker has been started interactively by user ted, better run as user x2gobroker. 2013-10-29 19:01:05,327 - broker - INFO - Automatically switching to DEBUG mode due to interactive launch of this application. usage: x2gobroker [-h] [-C CONFIG_FILE] [-b BIND_ADDRESS] [-d] x2gobroker: error: unrecognized arguments: --backend=inifile --user ted --task listsessions

On 10/29/13 11:00, x2go-user-request@lists.berlios.de wrote:

Send X2Go-User mailing list submissions to x2go-user@lists.berlios.de

To subscribe or unsubscribe via the World Wide Web, visit https://lists.berlios.de/mailman/listinfo/x2go-user or, via email, send a message with subject or body 'help' to x2go-user-request@lists.berlios.de

You can reach the person managing the list at x2go-user-owner@lists.berlios.de

When replying, please edit your Subject line so it is more specific than "Re: Contents of X2Go-User digest..."

Today's Topics:

1. Re: x2go session broker connect problem (Mike Gabriel)

---

Message: 1 Date: Tue, 29 Oct 2013 08:18:12 +0000 From: Mike Gabriel<mike.gabriel@das-netzwerkteam.de> To:x2go-user@lists.berlios.de Subject: Re: [X2Go-User] x2go session broker connect problem Message-ID: <20131029081812.Horde.okJoiab6YGTA8vs8g2sQGA2@mail.das-netzwerkteam.de>

Content-Type: text/plain; charset="utf-8"; Format="flowed"; DelSp="Yes"

Hi Ted,

On Fr 25 Okt 2013 19:28:11 CEST, Ted Barnes wrote:

...

Am trying to get up to speed on x2go session broker, but am having trouble. Any suggestions?

When try to connect I get:

Error Login failed! Please try again.

Along with... broker url:http://xxx.xxx.xxx.xxx/:8080/plain/inifilebroker url:http://xxx.xxxx.xxx.xxx/:8080/plain/inifile

For the X2Go Session Broker standalone daemon (python-tornado implementation) the X2Go Client cmdline is:

x2goclient --broker-url=http://<host>:8080/plain/inifile

...

or.... broker url:http://user@xxx.xxx.xxx.xxx/cgi-bin/x2gobroker.cfgi

For the WSGI implementation of X2Go Session Broker, the URL varies. For our default setup [1], use this X2Go Client cmdline:

x2goclient --broker-url=http://<host>/x2gobroker/plain/inifile

...

[...]

If you use the SSH implementation of X2Go Session Broker (available with 0.0.3.0, currently as preview in the nightly builds):

x2goclient --broker-url="ssh://<host>/usr/bin/x2gobroker --backend=inifile"

...

However, when I try from the command line with an "x2goclient --broker-..." type of command, I get the Error message.

This is not surprising me, as you have not used the correct URLs, so far.

...

x2gobroker-authservice (wasn't sure if I should install this for my initial tests)

Yes. The authentication system of the X2Go Session Broker uses PAM by default. PAM authentication requires root privileges. The X2Go Session Broker's Authentication Service runs with root privileges whereas the broker itself runs as user x2gobroker.

Greets, Mike

[1] http://code.x2go.org/gitweb?p=x2gobroker.git;a=blob;f=etc/x2gobroker-wsgi.ap...