You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Mike Jumper (Jira)" <ji...@apache.org> on 2020/08/11 08:41:00 UTC
[jira] [Commented] (GUACAMOLE-1153) Problem when printing with
Guacamole + RDP
[ https://issues.apache.org/jira/browse/GUACAMOLE-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175367#comment-17175367 ]
Mike Jumper commented on GUACAMOLE-1153:
----------------------------------------
Most likely WebSocket has not been correctly configured for the reverse proxy in front of your Guacamole instance. The HTTP tunnel that Guacamole must fall back on combined with the HTTP request for downloading the print job exceed the maximum number of HTTP requests that the browser allows, causing the browser to cease sending user input until the print job is complete, causing the connection to time out.
See: GUACAMOLE-506
If you correct your reverse proxy configuration, things should work fine. If you continue to have trouble with this, I suggest posting to the user@guacamole.apache.org mailing list for assistance.
> Problem when printing with Guacamole + RDP
> ------------------------------------------
>
> Key: GUACAMOLE-1153
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1153
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
> Affects Versions: 1.1.0
> Environment: Debian 10 - Windows 7 Terminal Service
> Reporter: Martin Vazquez
> Priority: Major
>
> I'ven following an issue that only occurs with some users.
> Im using Guacamole + RDP to connect to a Terminal Service. LDAP Auth is not actually configured.
> When I try to print with some users (ghstoscript installed, enable-printing set to true) it finishes the session.
> I've checked out /var/log/syslog and this is the message I get
>
> *Created PDF filter*
> *Running gs*
> *User is not responding*
> *Client did not terminate in a timely manner. Forcibly terminating client and any child processes*
>
> Any ideas why?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)