xpra icon
Bug tracker and wiki

Opened 3 weeks ago

Last modified 3 weeks ago

#1923 new defect

Using a proxy with Xpra

Reported by: ibuprofene Owned by: ibuprofene
Priority: major Milestone: 2.4
Component: server Version: 2.3.x
Keywords: Cc:

Description (last modified by Antoine Martin)

My goal is to setup a a proxy with xpra to run critical applications on behind a firewall. My three computers are running on Centos 7.5 and the version of xpra I use is v2.3.3-r19845. I installed it following the official doc: adding the repo and then sudo yum install xpra.

I have a first machine, my server, which is running xterm with xpra, I use the following command:

xpra start :100 --daemon=no --bind-tcp=0.0.0.0:10000 --start=xterm

The only error I have is:

2018-07-25 17:51:12,368 Error: failed to query sound subsystem:
2018-07-25 17:51:12,368  No module named sound.common

Now I go to the proxy:

xpra proxy :101 --tcp-auth=allow --bind-tcp=0.0.0.0:1203 --daemon=no

It works fine and says xpra is ready.

I finally go to the client and use:

xpra attach tcp/login@ip:1203/100

and i have the following:

xpra initialization error:
 failed to connect to '137.138.121.50:1203':
 [Errno 111] Connection refused

I know it cannot work because I didn't say to xpra proxy where is the server but I don't know where I can say that.
Thank you.

Change History (3)

comment:1 Changed 3 weeks ago by Antoine Martin

Component: androidserver
Description: modified (diff)
Milestone: 2.4
Owner: changed from Antoine Martin to ibuprofene

failed to connect to '137.138.121.50:1203':

If this is your proxy server IP, this should work.
Are you sure that this isn't blocked by the firewall?

Once you get past the firewall, you need to find a way to get the proxy to know about which sessions it is proxying for. Assuming that the servers it is proxying for are remote systems, your best bet is to use the sqlite backend. See #1488 for details.
The credentials used with sqlite do not require a corresponding user account on the proxy server system.

Last edited 3 weeks ago by Antoine Martin (previous) (diff)

comment:2 Changed 3 weeks ago by ibuprofene

Well thank you, indeed my port was closed even though I thought I opened it, anyway, now I have an other error:

2018-07-26 15:23:42,505 server failure: disconnected before the session could be established
2018-07-26 15:23:42,505 server requested disconnect: server error (failed to start a new session)
2018-07-26 15:23:42,515 Connection lost

But I guess this is because I hadn't connect the server to the proxy, so I'm going to follow instructions in #1488

comment:3 Changed 3 weeks ago by Antoine Martin

2018-07-26 15:23:42,505 server requested disconnect: server error (failed to start a new session)
But I guess this is because I hadn't connect the server to the proxy, so I'm going to follow instructions in #1488

Correct. It is trying to start a new session. You can get more detailed debug messages with -d server.

Last edited 3 weeks ago by Antoine Martin (previous) (diff)
Note: See TracTickets for help on using tickets.