[ 
https://issues.apache.org/jira/browse/GUACAMOLE-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769707#comment-16769707
 ] 

Andrew Lamarra commented on GUACAMOLE-733:
------------------------------------------

I've upgraded everything to version 1.0.0 and now I can't initiate a VNC 
connection. I can still connect to the VNC server via a regular vncviewer 
client on my network. Guacamole, however, just gives me the error: "The remote 
desktop server is currently unreachable. If the problem persists, please notify 
your system administrator or check your system logs."

I was able to obtain the following relevant logs from catalina.out:
{noformat}
15:24:19.422 [http-nio-8080-exec-5] INFO o.a.g.tunnel.TunnelRequestService - 
User "user" connected to connection "2".
15:24:24.480 [Thread-34] INFO o.a.g.tunnel.TunnelRequestService - User "user" 
disconnected from connection "2". Duration: 5057 milliseconds
15:24:27.081 [http-nio-8080-exec-10] INFO o.a.g.tunnel.TunnelRequestService - 
User "user" connected to connection "2".
Exception in thread "Thread-37" java.lang.IllegalStateException: Message will 
not be sent because the WebSocket session has been closed
        at 
org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:384)
        at 
org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessage(WsRemoteEndpointImplBase.java:341)15:24:27.207
 [http-nio-8080-exec-2] INFO
        o.a.g.tunnel.TunnelRequestService - User "user" disconnected from 
connection "2". Duration: 125 milliseconds

        at 
org.apache.tomcat.websocket.WsRemoteEndpointImplBase$TextMessageSendHandler.write(WsRemoteEndpointImplBase.java:759)
        at 
org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPartialString(WsRemoteEndpointImplBase.java:252)
        at 
org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:195)
        at 
org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:37)
        at 
org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint.sendInstruction(GuacamoleWebSocketTunnelEndpoint.java:152)
        at 
org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint.access$200(GuacamoleWebSocketTunnelEndpoint.java:53)
        at 
org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint$2.run(GuacamoleWebSocketTunnelEndpoint.java:253){noformat}
Also, I'm running Guacamole on a FreeNAS 11.2 iocage jail with Apache Tomcat & 
MariaDB.

Are there other logs I should be looking at to troubleshoot the issue?

> VNC Scaling Not working properly
> --------------------------------
>
>                 Key: GUACAMOLE-733
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-733
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-client, VNC
>    Affects Versions: 0.9.14
>         Environment: The VNC Server:
> Ubuntu 16.04.5 LTS
> TigerVNC
>            Reporter: Andrew Lamarra
>            Priority: Trivial
>              Labels: vnc
>
> Hi there. I've been using Guacamole for a couple of years now (and love it!), 
> but I've always had one issue. When connecting to a VNC server, the scaling 
> of the window has always been a bit awkward to me. It's really difficult to 
> get Guacamole to scale the display to 100%. I'm able to do so by following 
> these steps:
>  * Open the Guacamole menu (press Ctrl+Alt+Shift)
>  * Uncheck "Automatically fit to browser window" under Display
>  * Un-maxmize browser window
>  * Check "Automatically fit to browser window"
>  * Uncheck "Automatically fit to browser window"
> Now I'm at 100%. But I can't maximize the browser window or it'll change 
> (even though I have "Automatically fit to browser window" unchecked). It's a 
> minor annoyance because the font is noticeably fuzzy when not at 100%.
> Also, those zoom buttons don't work very well either. It only goes in 
> increments of 10%. And if you're at 109% and zoom out, then you're set to 
> 99%...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to