guac 1.5.1 failed to access k8s

[miao <go...@163.com>]

THX for 1.5.1 image. My vnc worked on it . But k8s does not work with 1.5.1. I’m not sure any conf I missed.


My env. Run kind on my Mac docker, and run a service in kind.

Pod httpd-dep-65d64d47c5-78x9c running in default namespace.



And service worked well


Kind inspect



Then, I put params in guacamole, and get error to access. All config was from .kube/config.





Error log in guard

2023-04-25 15:12:43 guacd[1900]: ERROR: Error connecting to Kubernetes server: conn fail: 111
2023-04-25 15:12:43 guacd[1900]: INFO:  User "@3e594de2-8121-4f10-b9bb-f8fd3c4b7ddf" disconnected (0 users remain)
2023-04-25 15:12:43 guacd[1900]: INFO:  Last user of connection "$97cebdb7-303b-4a2a-a553-32533e482b44" disconnected
2023-04-25 15:12:44 guacd[1900]: INFO:  Kubernetes connection ended.
2023-04-25 15:12:44 guacd[1]: INFO:     Connection "$97cebdb7-303b-4a2a-a553-32533e482b44" removed.



Any suggestions.

Thanks a lot.



> 2023年4月24日 01:39，Michael Jumper <mj...@apache.org> 写道：
> 
> Give the 1.5.1 images a try. There was a VNC auth regression in the 1.5.0 Docker images that was fixed in 1.5.1:
> 
> https://guacamole.apache.org/releases/1.5.1/
> 
> - Mike
> 
> On Sun, Apr 23, 2023, 6:39 AM Simon <gogo6754@163.com <ma...@163.com>> wrote:
>> hi,
>>     sry for double click.
>> 
>>      I have run guac in docker, version 1.5.0 and in db model.
>>     When vnc's authentication username and password, it worked well. but when authenticaiton only password, do not work at all.
>> 
>>     guacd error log
>>  
>>   
>> 
>>   pls give me a hand. Thx.
>> 
>> 
>> 
>> 
> <WX...@2x.png>

Re: guac 1.5.1 failed to access k8s

[Nick Couchman <vn...@apache.org>]

On Tue, Apr 25, 2023 at 3:15 AM miao <go...@163.com> wrote:

> THX for 1.5.1 image. My vnc worked on it . But k8s does not work with
> 1.5.1. I’m not sure any conf I missed.
>
>
> My env. Run kind on my Mac docker, and run a service in kind.
>
> Pod httpd-dep-65d64d47c5-78x9c running in default namespace.
>
> [image: 粘贴的图形-1.png]
>
> And service worked well
> [image: 粘贴的图形-2.png]
>
> Kind inspect
> [image: 粘贴的图形-3.png]
>
>
>
So, the thing that I notice, here, is that, while port 30000 shows
listening on 0.0.0.0:30000, port 54361 shows it only listening on the
loopback interface, which means it will only be accessible from the system
where K8s is actually running, and maybe not even from other containers on
that same host. This could limit Guacamole's ability to connect, depending
on where you're connecting from. You might try reconfiguring that to
0.0.0.0:54361 and see if that works.

-Nick