Re: disabled web interface

2018-09-21 Thread Mike Jumper
You're definitely not the only one to have been confused by this behavior.
It was recently corrected:

https://issues.apache.org/jira/browse/GUACAMOLE-508

In future releases, Guacamole will not automatically connect if the user
has admin privileges. It will only automatically connect for users that
have absolutely no access to anything but a single connection, taking into
account access to admin pages.

- Mike


On Fri, Sep 21, 2018 at 2:44 AM Galyrith 
wrote:

> Ho...
> i feel stupid...
> thank for this quick response!
>
>
>
> --
> Sent from:
> http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/
>


Re: VNC connection problem

2018-09-21 Thread Mike Jumper
As Nick suggests, please verify that you are not accidentally configuring
the connection to attempt to connect to the VNC server as if it is guacd.
The fields in the web interface for the guacd hostname/port and the VNC
server hostname/port are fairly close together, so this would be an easy
mistake to make. If you did accidentally specify the VNC server
hostname/port for the guacd hostname/port, the protocol error you see in
catalina.out is exactly what would be expected.

- Mike


On Sep 19, 2018 14:02, "VolandSZ"  wrote:

Any ideas?




--
Sent from:
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/


Re: disabled web interface

2018-09-21 Thread Galyrith
Ho...
i feel stupid...
thank for this quick response!



--
Sent from: 
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/


Re: disabled web interface

2018-09-21 Thread Stefan M. Radman
Salut Quentin

That is the typical behavior when you have configured only one connection.

Use the Guacamole menu to navigate back to the home screen.

https://guacamole.apache.org/doc/gug/using-guacamole.html#guacamole-menu

You can reach it with Ctrl+Alt+Shift while logged in (on the Mac use 
Shift-Ctrl-Cmd).

Stefan

> On Sep 21, 2018, at 11:09 AM, Galyrith  wrote:
> 
> Hi,
> 
> First sorry for my approximate english.
> I explain my problem:
> I installed guacamole in my CentOS 7 with this tuto
> https://robertpascal.github.io/guacamole/.
> It works properly but when i configure a connection (ssh for exemple), i
> can't go back to the web interface.
> When i log in, i stay on the ssh connection and when i log out, i only have
> to disconnect or reconnect.
> 
>  
> 
> 
> 
> --
> Sent from: 
> http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/



disabled web interface

2018-09-21 Thread Galyrith
Hi,

First sorry for my approximate english.
I explain my problem:
I installed guacamole in my CentOS 7 with this tuto
https://robertpascal.github.io/guacamole/.
It works properly but when i configure a connection (ssh for exemple), i
can't go back to the web interface.
When i log in, i stay on the ssh connection and when i log out, i only have
to disconnect or reconnect.

 



--
Sent from: 
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/


Re: "Error handling message from VNC server" in Debian based builds

2018-09-21 Thread Ou Changkun
I am not 100% sure it is GUACAMOLE-414. However, what I can observed in the VNC 
server is attached in below. The log (tigerVNC) pretty much similar to what 
GUACAMOLE-414 reported:

Connections: closed: 172.16.250.10::51164 (readTLS: (unknown error code)(1100))

I will digging more infos.

==

Fri Sep 21 15:10:51 2018
 VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
 VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian rgb888

Fri Sep 21 15:10:55 2018
 Connections: closed: 172.16.250.10::51164 (readTLS: (unknown error code)
  (1100))
 EncodeManager: Framebuffer updates: 123
 EncodeManager:   RRE:
 EncodeManager: Solid: 113 rects, 1.77475 Mpixels
 EncodeManager:2.20703 KiB (1:3141.75 ratio)
 EncodeManager:   ZRLE:
 EncodeManager: Bitmap RLE: 6 rects, 290 pixels
 EncodeManager: 178 B (1:6.92135 ratio)
 EncodeManager: Indexed RLE: 465 rects, 9.15282 Mpixels
 EncodeManager:  65.917 KiB (1:542.48 ratio)
 EncodeManager: Full Colour: 338 rects, 9.38646 Mpixels
 EncodeManager:  2.01581 MiB (1:17.7648 ratio)
 EncodeManager:   Total: 922 rects, 20.3143 Mpixels
 EncodeManager:  2.08251 MiB (1:37.2164 ratio)
 TLS: TLS session wasn't terminated gracefully
 ComparingUpdateTracker: 47.898 Mpixels in / 20.9308 Mpixels out
 ComparingUpdateTracker: (1:2.28839 ratio)

On Sep 20, 2018, at 20:41, Mike Jumper 
mailto:mjum...@apache.org>> wrote:

If you are encountering GUACAMOLE-414, and feel like tinkering in the source, I 
suspect things might have to do with some versions of OpenSSL needing 
process-wide initialization of thread safety, similar to what is done in the 
SSH client.

Worth checking whether making that change solves things.

- Mike

On Thu, Sep 20, 2018, 11:16 Ou Changkun 
mailto:ouchang...@outlook.com>> wrote:
Close this question, issue was reported to dev channel: 
https://issues.apache.org/jira/projects/GUACAMOLE/issues/GUACAMOLEf-414

On Sep 20, 2018, at 01:57, Ou Changkun 
mailto:ouchang...@outlook.com>> wrote:

Hi Jeff,

Thanks for your response. However that doesn’t help too much. I know where to 
find a typical log file, VNC logs are missing in /var/log. That’s the reason I 
post question for help.

Could you maybe try the provided only three reproduce steps yourself to see 
what is going on?

Best,
Changkun

On Sep 19, 2018, at 23:41, McRoy, Jeffrey (GE Healthcare) 
mailto:jeffrey.mc...@ge.com>> wrote:

Sounds like you setup an Ubuntu container to run the VNC server in. So, in 
Linux the log files typically go in the directory /var/log. You could look 
there. Try this to look for files with vnc entries: grep vnc /var/log/* -R | 
less

You could also try tailing the messages log file in Ubuntu while you try to 
connect to the vnc server: tail -f /var/log/messages.log

It might help to see what the vnc server is logging when you try to connect 
with the client.


Regards,
-Jeff



From: Ou Changkun mailto:ouchang...@outlook.com>>
Reply-To: "user@guacamole.apache.org" 
mailto:user@guacamole.apache.org>>
Date: Wednesday, September 19, 2018 at 2:44 PM
To: "user@guacamole.apache.org" 
mailto:user@guacamole.apache.org>>
Subject: EXT: Re: "Error handling message from VNC server" in Debian based 
builds

Hi Jeffrey,

Could you maybe tell where is the location of VNC log files and what exactly 
you want for log?

Here is all I get from `docker log` command:

USER_ID: 1000, GROUP_ID: 0
nss_wrapper location: /usr/lib/libnss_wrapper.so

-- update chromium-browser.init --

... set window size 1280 x 1024 as chrome window size!


-- change VNC password  --

-- start noVNC  

-- start VNC server 
remove old vnc locks to be a reattachable container
start vncserver with param: VNC_COL_DEPTH=24, VNC_RESOLUTION=1280x1024
...
start window manager
...


-- VNC environment started --

VNCSERVER started on DISPLAY= :1
=> connect via VNC viewer with 
172.16.250.11:5901


On Sep 19, 2018, at 20:52, McRoy, Jeffrey (GE Healthcare) 
mailto:jeffrey.mc...@ge.com>> wrote:

Hi Changkun,

Could you attach the log from the VNC server?