Xpra: Ticket #1045: HTML5 Client Intro page loops

Have run xpra server (ref: http://xpra.org/trac/wiki/Clients/HTML5) with:

XPRA_RANDR=0 xpra start :10 \
    --xvfb="Xorg -noreset -nolisten tcp +extension GLX \
    -config /etc/xpra/xorg.conf \
    +extension RANDR +extension RENDER \
    -logfile ${HOME}/.xpra/Xorg-10.log" \
    --sync-xvfb=50  --sharing=yes \
    --bind-tcp=localhost:10000 --html=on \
    --start=libreoffice


Accessing http://localhost:10000 gives me the same default form page in loop instead of the running libreoffcie even after I filled the form many a times as in the attached screenshot.


Websockify is installed:

$ dpkg -l | grep ii | grep websockify
ii  websockify                                 0.5.1+dfsg1-3ubuntu0.14.04.1                                amd64        WebSockets support for any application/server


All ports are open in the server.



Tue, 01 Dec 2015 09:45:59 GMT - zenny: attachment set

xpra html5 client loops to the same intro page.


Tue, 01 Dec 2015 10:05:01 GMT - Antoine Martin: owner changed

The problem is immediately obvious from the server log file, this should be fixed in r11343. You can also use a stable 0.15.x version, which does not have this problem.

Warning: localhost is not a valid IP address and should not be used, the server does give you a warning about this in the log file. It only works by accident because the safe fallback is "127.0.0.1".

BTW, none of these things are relevant to this ticket and only make things more complicated than they need to be:

You can reproduce the problem with just:

xpra start :10 --bind-tcp=127.0.0.1:10000 --html=on --start=xterm
xdg-open http://127.0.0.1:1000/

Tue, 01 Dec 2015 12:16:40 GMT - zenny:


You can also use a stable 0.15.x version, which does not have this problem.

Thank you for the pointer, but I cannot roll back to 0.15.x because I need some features available only in 0.16 beta.


Warning: localhost is not a valid IP address and should not be used,


I didn't use localhost, but the IP of the xpra server which you can see in the attached screenshot (http://192.168.10.3:10000)

The problem is immediately obvious from the server log file, this should be fixed in r11343.


Yep, I shall try with that patch.


Tue, 01 Dec 2015 12:18:42 GMT - Antoine Martin:

I didn't use localhost, ..


Your command line definitely does. See your own ticket description.


Tue, 01 Dec 2015 12:24:00 GMT - zenny:

Your command line definitely does.

But the IP address of the server has been replaced by localhost to make things at par with the documentation. But the screenshot attached to that ticket does not.

Anyway, there is nothing to argue as you already pointed out that should be fixed in r11343. Thanks for the pointer.


Tue, 01 Dec 2015 12:36:48 GMT - Antoine Martin:

But the IP address of the server has been replaced by localhost to make things at par with the documentation.


That does not make any sense: there is nothing anywhere on the wiki with localhost used with the "bind-tcp" option, as this would be invalid.

The only 2 hits when you search for "bind-tcp=localhost" are your own tickets.


But the screenshot attached to that ticket does not.


The screenshot shows the browser (and browsers obviously handle DNS names), not the "bind-tcp" option which is an xpra command line.


Tue, 08 Dec 2015 05:08:27 GMT - Antoine Martin: status changed; resolution set

I assume this is fixed. Closing.


Sat, 23 Jan 2021 05:13:24 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1045