Re: How to upgrade Guacamole 1.0 to 1.3 on Ubuntu

[Mike Jumper]

On Tue, Aug 17, 2021 at 7:57 AM Roman Adyev  wrote:

> Thank you very much for the pointer but unfortunately I didn't find any
> article concerning update procedure there, only:
>
> Installing
>
> Configuring
>
> Administration
>
> Troubleshooting
>
> Etc.
>

To upgrade a native installation of 1.0.0 to 1.3.0, you go through the
installation steps again, effectively replacing your existing install with
the new one. The configuration files, their locations, etc. are all the
same, so you don't need to make any other changes beyond building the newer
guacamole-server, deploying the new .war, and updating your extensions.

If you were upgrading from a release prior to 1.0.0 like 0.9.14, there
would also be schema changes that need to be applied, but that will not be
the case for upgrading any 1.x release to any later 1.x release. If ever
the schema changes again, that release would get a full major number bump.

- Mike

Re: guacamole broken on Safari

[Mike Jumper]

This should now be fixed via
https://github.com/apache/guacamole-client/pull/639. The issue was that an
old CSS class, "tiled-client-list", was replaced with a corresponding
directive, "guac-tiled-clients" via commit c990043, but the style rule that
referenced "tiled-client-list" was not updated accordingly.

Michael Jumper
CEO, Lead Developer
Glyptodon Inc .


On Mon, Aug 16, 2021 at 8:46 PM Mike Jumper 
wrote:

> OK - after installing a copy of OS X "Catalina" within VirtualBox, I'm now
> able to reproduce this on the included older version of Safari. I'll start
> digging into what CSS changes are needed to un-break older Safaris.
>
> Michael Jumper
> CEO, Lead Developer
> Glyptodon Inc .
>
>
> On Fri, Aug 13, 2021 at 6:03 AM Leo Nikolaev 
> wrote:
>
>> Okay, I think this could be closed.
>>
>> I’ve done the tests, only the old versions of Safari are affected: 14.0
>> and below. As long as we have a relatively small share of old Safafi
>> browsers.
>>
>> Btw, I’ve tracked down the bug in current master, it all comes to wrong
>> heigth, which is not firing from somewhere deep inside tiles.
>>
>> Mike, thanks for your help :)
>>
>> Cheers,
>> Leo
>>
>> > On 13 Aug 2021, at 00:42, Mike Jumper 
>> wrote:
>> >
>> > On Wed, Aug 11, 2021 at 2:52 PM Leo Nikolaev 
>> wrote:
>> > You mean I should not see this issue on latest master? Is there a
>> different code there?
>> >
>> > The code on master should be the same code that you bisected - it just
>> happens that code from the specific commit that you found through the
>> bisect was already effectively undone by a later commit that would also
>> have been in the history when you did the bisect.
>> >
>> > All this means is that the result of the bisect is not as
>> straightforward as would be ideal.
>> >
>> > - Mike
>> >
>>
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
>> For additional commands, e-mail: user-h...@guacamole.apache.org
>>
>>

Re: RDP From Guac in Docker to LXC Container

[Matthew Lawson]

Use it as much as you like 

I’ll try out your method tonight or tomorrow.

I appreciate the help.

~ML
On Aug 16, 2021, 5:20 PM -0400, Ivanmarcus , 
wrote:
> Matthew,
>
> Great analogy, do you mind if I pinch it? I could use something like
> that a lot! ;-)
>
> To simply try what you've got, on the same host IP, here's a suggestion
> from a terminal on your host machine:
>
> docker run -it -h cn1 --net host -p 3389:3389 cn1 /bin/bash
>
> This should start up the cn1 container with the same IP address as your
> host, expose 3389 internal to 3389 external, and drop you in a bash
> shell on that container. Once you're happy with that just ctrl-p ctrl-q
> to exit, but leave the container running.
>
> I've assumed the name 'cn1' for your container here, but you can
> obviously use whatever is correct. The -h parameter will name the
> running container 'cn1' too, otherwise it'll just give you a weird name
> (which is fine, you'd just need to use docker ps to find it!).
>
> Then:
>
> docker run -it -h guacamole --net host -p 8080:8080 guacamole /bin/bash
>
> Same as with cn1, except this'll expose internal port 8080 to external
> port 8080.
>
> Again, once running & checked you can just ctrl-p ctrl-q to exit.
>
> From there you should now be able to access both containers on their
> respective ports. First using Remmina to cn1 (host IP address, port
> 3389) then, assuming cn1 is working, browse to host IP address port 8080
> and see if you get Guacamole, the rest should follow from there.
>
> Using the parameters I've given means you should later be able to
> connect in to the containers from a terminal using something like:
>
> docker container exec -it [container name] /bin/bash
>
> Then you can do/check whatever you need and just type 'exit' whenever
> you're finished to be dropped back to the host terminal *without*
> closing the container.
>
> Note I've *not* tried this and I could be leading you up a long and
> winding path so perhaps asking some real girls and boys on those forums
> is advisable - still no harm in trying this I guess...
>
>
>
> On 17/08/21 3:04 am, Matthew Lawson wrote:
> > You may not be a Docker expert, but you know more than me about it.
> > What I know about docker and networking can be summed up as follows:
> >
> > user:~$ cat ~/network-and-docker-knowledge.txt
> > cat: /home/user/network-and-docker-knowledge.txt: No such file or directory
> > user:~$
> >
> > I'll give your suggestion a try once I find some resources to explain
> > how I might do it.
> >
> > In the meantime, I think I'll cross-post this question on the Docker and
> > LXC/LXC forums.
> >
> >
> > ~ML
> >
> > On Monday, August 16, 2021, Ivanmarcus  wrote:
> >
> > Great, that's made it a bit easier to fault-find.
> >
> > Unfortunately I'm not a Docker expert, and have never had anything
> > to do with LXD, so I'd treat anything I say from here with suspicion!
> >
> > In the interests of keeping things simple, I've tended to try and
> > keep any Docker containers as standalone instances on the same
> > common subnet as I might normally. This may not be the strictly
> > approved way, but it works for me.
> >
> > To that end I would restart the Guacamole and cn1 Docker instances
> > with their own ip address on your normal subnet (eg. 192.168.1.xxx).
> > This would avoid the need to go through any routing drama and should
> > mean that everything, including your host machine, can see
> > everything else.
> >
> > I've done this in the past either via the cli, or alternatively with
> > a docker-compose file uisng macvlan.
> >
> > Alternatively you could also use the host option and just assign
> > different ports as you need to the Docker instances and keep them
> > all on the same IP address. For instance cn1 may only need port 3389
> > accessible, and Guacamole port 8080 which means both can be on the
> > (same) host IP. It's also possible to alias the ports too, but
> > probably no need here.
> >
> > With luck someone with a lot more clues than me will come along
> > shortly and suggest a better way, but in the meantime you could give
> > this a try as I've had good success with this methodology.
> >
> >
> > On 16/08/21 1:20 pm, Matthew Lawson wrote:
> >
> > Remmina connected to cn1 right away.
> >
> > Does the routing path look something like this:
> > Guac on Docker ==> Docker Bridge ==> Host Network ==> LXD Bridge
> > ==> cn1?
> >
> >
> > ~ML
> > On Aug 15, 2021, 8:24 PM -0400, Ivanmarcus
> > , wrote:
> >
> > Matthew,
> >
> > There could be a few reasons for this issue, but in
> > fault-finding I
> > guess I'd start with first trying a direct RDP connection to
> > cn1 (ie.
> > not via Guacamole).
> >
> > Not sure if you're using a Linux or Win machine, but I find
> > Remmina is a
> > good Linux tool for testing RDP and VNC connections.
> >
> > That should at least give you an idea if cn1 is performing
> > as it should,
> > and therefore potentially narrow down where you need to look
> > for the
> > problem. All that 

RE: How to upgrade Guacamole 1.0 to 1.3 on Ubuntu

[Roman Adyev]

Thank you very much for the pointer but unfortunately I didn't find any article 
concerning update procedure there, only:

Installing 

Configuring

Administration

Troubleshooting

Etc.

 

From: Nick Couchman  
Sent: Tuesday, August 17, 2021 5:08 PM
To: user@guacamole.apache.org
Subject: Re: How to upgrade Guacamole 1.0 to 1.3 on Ubuntu

 

On Tue, Aug 17, 2021 at 9:46 AM Roman Adyev mailto:adro...@yandex.ru> > wrote:

Guys, is there any sort of manual ?

 

Yes: http://guacamole.apache.org/doc/gug/

 

Should I uninstall 1.0 first or it’s possible to upgrade somehow?

 

 

You should not need to uninstall - upgrading is definitely possible.

 

-Nick 

Re: How to upgrade Guacamole 1.0 to 1.3 on Ubuntu

[Nick Couchman]

On Tue, Aug 17, 2021 at 9:46 AM Roman Adyev  wrote:

> Guys, is there any sort of manual ?
>

Yes: http://guacamole.apache.org/doc/gug/


> Should I uninstall 1.0 first or it’s possible to upgrade somehow?
>
>
>

You should not need to uninstall - upgrading is definitely possible.

-Nick

Re: Automate login and establishing of RDP connection

[Nick Couchman]

On Tue, Aug 17, 2021 at 9:06 AM FelixD 
wrote:

> Hello,
> I’m trying to automate the steps of logging in into Guacamole and starting
> up a connection so that a user doesn’t have to interact with  Guacamole
> itself.
> So that in the end I would be able to send a request to guacamole that
> logs in the user and start the connection stored on that account.
>
>
This is a little bit of an ambiguous request. Perhaps you can be more
specific about what exactly you want to do. Here are some things to keep in
mind:
* If a user only has one connection assigned in Guacamole, that connection
will launch automatically as soon as they log in to Guacamole.
* Each connection has a unique URL that can be used to launch that
particular connection. The user will log in to Guacamole and then get
automatically directed to the connection.
* Don't try to disable authentication in Guacamole. Integrate it with SSO
or LDAP or whatever you have to do, but do not disable it (
http://guacamole.apache.org/faq/#disable-auth).
* Parameter tokens are your friend, and will help make integration and user
experience more seamless:
http://guacamole.apache.org/doc/gug/configuring-guacamole.html#parameter-tokens

The header authentication module is available and does work - if you're
having trouble getting it set up, post back the steps you've done and what
behavior you're seeing and we can help you through that.

-Nick

How to upgrade Guacamole 1.0 to 1.3 on Ubuntu

[Roman Adyev]

Guys, is there any sort of manual ?

Should I uninstall 1.0 first or it's possible to upgrade somehow?

 

Automate login and establishing of RDP connection

[FelixD]

Hello,
I’m trying to automate the steps of logging in into Guacamole and starting up a 
connection so that a user doesn’t have to interact with  Guacamole itself.
So that in the end I would be able to send a request to guacamole that logs in 
the user and start the connection stored on that account.

Is there anything in place that might help me with that ?
I found an old discussion about autologin through URL but it seems deprecated ?

If there is no existing feature capable of this I tough of creating a custom 
extension which takes part from the ad Hoc & Header auth extensions and merges 
them into one system.

But I cant get the Header authentication itself to work.

I would appreciate if someone could share an example or some documentation on 
the header authentication.  
I’m using the default authentication module that guacamole provides.

~Felix D.