You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Michael Jumper (JIRA)" <ji...@apache.org> on 2019/01/10 19:52:00 UTC
[jira] [Commented] (GUACAMOLE-695) clone a connection puts hostname
as guacamole proxy parameter
[ https://issues.apache.org/jira/browse/GUACAMOLE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739728#comment-16739728 ]
Michael Jumper commented on GUACAMOLE-695:
------------------------------------------
No worries - thanks for testing. We don't make updates to past releases except through new releases, so if this is not an issue with 1.0.0, then it's fixed and there's nothing for us to resolve. Definitely let us know if it reappears, though.
> clone a connection puts hostname as guacamole proxy parameter
> -------------------------------------------------------------
>
> Key: GUACAMOLE-695
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-695
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
> Affects Versions: 0.9.14
> Reporter: dave wentzel
> Priority: Minor
>
> haven't tried this on 1.0, yet. UPDATE: 1.0 docker containers do NOT have this issue. you can decide if you want to resolve. Sorry to be a pest.
> I'm running 0.9.14 with docker. I have a working RDP entry that I clone. All I usually do when I do this is change the Parameters|Network|Hostname to my new server (doesn't matter but it's lxc running xrdp and I can connect from windows).
> Issue is the process of cloning puts the hostname entry in the "Guacamole Proxy Parameters (GUACD)" section too, which then causes more gray hair trying to troubleshoot.
> Fixing that and everything is back to normal. I'll update my docker to 1.0 and see if that affects anything in a bit.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)