guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Herold <martin.her...@procal.de>
Subject Re: guacamole docker rdp printing issue
Date Fri, 11 Jan 2019 08:18:43 GMT
is it pssible to check on client-side the state of connection? If it is 
http or websocket?

Regards
Martin


----------------------
Martin Herold
Mystical Datentechnik GbR
Helmholtzstraße 11
D-71573 Allmersbach
Telefon: +49 7191 911405
Telefax: +49 7191 911777
EMail: martin.herold@procal.de

Am 09.01.2019 um 19:15 schrieb Christian Kraus:
> AW: guacamole docker rdp printing issue
>
> thanks
>
>
> that was the problem - no websocket connecction only http
>
> sorry for that - as i always setup websocket - but this time it was 
> with univention ucs server and the guacamole cool solution there 
> overwrites my proxy conf file without websocket section (i already 
> informed them to change the guacamole.conf template)
>
>
>
> rg
>
> Christian
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>     -----Ursprüngliche Nachricht-----
>     *Von:* Mike Jumper <mjumper@apache.org>
>     *Gesendet:* Mittwoch 9 Januar 2019 18:29
>     *An:* user@guacamole.apache.org
>     *Betreff:* Re: guacamole docker rdp printing issue
>
>     On Wed, Jan 9, 2019, 03:52 Christian Kraus
>     <christian.kraus@ckc-it.at <mailto:christian.kraus@ckc-it.at> wrote:
>
>         Hi,
>
>
>         I deployed guacamole through docker with latest edition
>         (0.9.14) (guacd docker and sql docker) and getting printing
>         not realy to work with rdp printing enabled
>
>
>         it only works on small files like text file with only a few
>         words in - docs with more content don't get printed at all -
>         when leaving the connection a download of the print is
>         provided - but that is corrupt file
>
>
>     You are likely running into:
>
>     https://issues.apache.org/jira/browse/GUACAMOLE-506
>
>
>         any suggestions on this ?
>
>
>     Assuming you are hosting Guacamole behind  a reverse proxy,
>     recheck your proxy configuration to make sure WebSocket is
>     properly set up.
>
>     Depending on your network, it is also possible that something
>     between the client machine and Guacamole (such as a corporate
>     proxy or firewall) does not properly support WebSocket and is
>     forcing Guacamole to fall back to HTTP.
>
>     - Mike
>


Mime
View raw message