xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.


Opened 3 years ago

Last modified 4 months ago

#1923 closed defect

Using a proxy with Xpra — at Initial Version

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

Description

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 whre I can say that.
Thank you.

Change History (0)

Note: See TracTickets for help on using tickets.