xpra icon
Bug tracker and wiki

Custom Query (2402 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (28 - 30 of 2402)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Ticket Resolution Summary Owner Reporter
#2656 invalid Question html5 clients with proxy and ssl Antoine Martin peter0914
Description

Hello,

I want multiple html5 web-clients be able to connect through a single port (8080) and reach their individual xpra session. I have successfully built this setup using:

sqlite_auth.py xpra-auth.sdb create
sqlite_auth.py xpra-auth.sdb add user1 pass1 user1 user1 tcp://localhost:10101/

sudo xpra proxy :10100 --bind-tcp=0.0.0.0:8080 --html=on --socket-dir=/tmp --no-daemon --tcp-auth=sqlite,filename=./xpra-auth.sdb
xpra start :10101 --bind-tcp=0.0.0.0:10101 --no-daemon

-> http://domain:8080/index.html?username=user1&password=pass1

However, if I enable SSL it fails:

sqlite_auth.py xpra-auth.sdb create
sqlite_auth.py xpra-auth.sdb add user1 pass1 user1 user1 tcp://localhost:10101/
sudo xpra proxy :10100 --bind-ssl=0.0.0.0:8080 --ssl=www --ssl-key=privkey.pem \
	--ssl-cert=fullchain.pem --html=on --socket-dir=/tmp --no-daemon \
	--tcp-auth=sqlite,filename=./xpra-auth.sdb
xpra start :10101 --bind-tcp=0.0.0.0:10101 --no-daemon

-> https://domain:8080/index.html?username=user1&password=pass1

The proxy error message is:

2020-03-19 14:40:40,161 Error: the proxy server requires an authentication mode,
2020-03-19 14:40:40,161  client connection 'wss' does not specify one
2020-03-19 14:40:40,161  use 'none' to disable authentication

How can SSL/WSS be enabled for this setup?

#2654 fixed xpra-auto-display: don't use "low display numbers" Antoine Martin stdedos
Description

I have seen xpra auto-assume low number displays:

u@h:/etc/xpra/conf.d$ xpra start --attach=yes --start=gnome-terminal
xpra for python 2.7 is not installed
 retrying with python3
Entering daemon mode; any further errors will be reported to:
  /run/user/1000/xpra/display-S6777-$TIMESTAMP.log
u@h:/etc/xpra/conf.d$ Actual display used: :4
Actual log file name is now: /run/user/1000/xpra/display-:4-$TIMESTAMP.log
u@h:/etc/xpra/conf.d$ xpra upgrade :4
xpra for python 2.7 is not installed
 retrying with python3
WARNING: low display number: 4
 You are attempting to run the xpra server
 against a low X11 display number: ':4'.
 This is generally not what you want.
 You should probably use a higher display number
 just to avoid any confusion and this warning message.
Entering daemon mode; any further errors will be reported to:
  /run/user/1000/xpra/display-:4-$TIMESTAMP.log

... and when upgrading, this happens. Is it a problem if xpra becomes pedantic and prefer higher number displays? (I think it was >:10 or something?)

#2653 worksforme xpra upgrade :0 looks like a bad idea stdedos stdedos
Description

I updated /etc/xpra/conf.d/80_lock.conf configuration file, and I was thinking how could I quickly update the server without stop/shadow.

Without much thinking I did xpra upgrade :0.

Now theming is different, fonts are different and applications have duplicated "File" menus (one in the normal Unity toolbar, one just when their drawing area starts).

Maybe I shouldn't be able to do that? Or you do it internally like a stop/shadow instead?

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Note: See TracQuery for help on using queries.