On Thu, Apr 25, 2019 at 12:31 PM Lance Gropper < lance.grop...@encorehollywood.com> wrote:
> Hello All: > > > > Apr 25 09:27:10 guacamole-post server: 09:27:10.400 > [http-bio-8080-exec-10] INFO o.a.g.tunnel.TunnelRequestService - User > "test" connected to connection "DDR22". > > Apr 25 09:27:10 guacamole-post guacd[31535]: ConnectClientToTcpAddr6: > connect > > Apr 25 09:27:10 guacamole-post guacd[31535]: ConnectToTcpAddr: connect > > Apr 25 09:27:10 guacamole-post guacd[31535]: Unable to connect to VNC > server > > Apr 25 09:27:10 guacamole-post guacd[31535]: Unable to connect to VNC > server. > > Apr 25 09:27:10 guacamole-post kernel: guacd[31538]: segfault at 10 ip > 00007f9a8d526df2 sp 00007f9a8df32b90 error 4 in > libguac-client-vnc.so.0.0.0[7f9a8d51e000+13000] > A couple of things, here: - Have you verified that you can connect to the VNC server with some other VNC client from the same system (or at least the same network) where guacd is running? - I believe there was a VNC segfault issue present prior to 1.0.0 that was resolved in 1.0.0. I'd have to dig back through the list of changes in 1.0.0, but I seem to recall this. - There's a small bug regarding VNC + TLS connections (GUACAMOLE-414) that just got merged into the git tree, that'll be fixed in 1.2.0 when that comes out later this year. -Nick >
