Guacamole on Fedora 27



  • Installing Docker as Described Here:

    https://docs.docker.com/install/linux/docker-ce/fedora/

    Everything seems to work.

    Then setup Guacamole as described here:

    https://linode.com/docs/applications/remote-desktop/remote-desktop-using-apache-guacamole-on-docker/#initialize-guacamole-authentication-with-mysql

    Everything seems to work pefectly, but http://HOSTNAME:8080/guacamole/ doesn't load.

    I disabled the firewall, made no difference.

    https://guacamole.apache.org/doc/gug/guacamole-docker.html



  • SELinux blocking it?



  • @black3dynamite snap, could be...



  • Works fine in Ubuntu 😕



  • @aaronstuder said in Guacamole on Fedora 27:

    Works fine in Ubuntu 😕

    Did you try setting SELinux to permissive?



  • @black3dynamite Not yet. Hopefully I’ll be able to try it again soon.



  • I’ll try this again tomorrow



  • @aaronstuder

    Check NoVNC it is much easier and simpler project and provides same functionality but poorer visual but I think better reliability cause it is simpler.

    https://www.server-world.info/en/note?os=Fedora_27&p=desktop&f=8



  • I've tried Guacamole on CentOS and Debian. Both worked fine, but it was a bare-metal install (not docker). Check Guacamole and Tomcat logs to identify if they are running at all and try to see your connection attempts there. If there is nothing it has to be firewall/connectivity issue.



  • I have did the same as above. My issue is with the VNC / SSH connection. Any pointer for resolving?

    From the link given, i am not able to create the tunnel as well
    ssh -L 5901:localhost:5901 -N -f -l user example.com

    my guacamole log:
    Exception in thread "Thread-52" java.lang.IllegalStateException: Message will not be sent because the WebSocket session has been closed
    at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:381)
    at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessage(WsRemoteEndpointImplBase.java:338)
    at org.apache.tomcat.websocket.WsRemoteEndpointImplBase$TextMessageSendHandler.write(WsRemoteEndpointImplBase.java:730)
    at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPartialString(WsRemoteEndpointImplBase.java:250)
    at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:193)
    at org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:37)
    at org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint$2.run(GuacamoleWebSocketTunnelEndpoint.java:167)
    01:51:38.736 [http-nio-8080-exec-5] INFO o.a.g.tunnel.TunnelRequestService - User "natrayan" connected to connection "1".
    01:51:38.784 [http-nio-8080-exec-6] INFO o.a.g.tunnel.TunnelRequestService - User "natrayan" disconnected from connection "1". Duration: 48 milliseconds
    01:51:54.722 [http-nio-8080-exec-7] INFO o.a.g.tunnel.TunnelRequestService - User "natrayan" connected to connection "1".
    Exception in thread "Thread-56" java.lang.IllegalStateException: Message will not be sent because the WebSocket session has been closed
    01:51:54.769 [http-nio-8080-exec-3] INFO o.a.g.tunnel.TunnelRequestService - User "natrayan" disconnected from connection "1". Duration: 46 milliseconds
    at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:381)
    at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessage(WsRemoteEndpointImplBase.java:338)
    at org.apache.tomcat.websocket.WsRemoteEndpointImplBase$TextMessageSendHandler.write(WsRemoteEndpointImplBase.java:730)
    at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPartialString(WsRemoteEndpointImplBase.java:250)
    at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:193)
    at org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:37)
    at org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint$2.run(GuacamoleWebSocketTunnelEndpoint.java:167)
    01:52:10.692 [http-nio-8080-exec-2] INFO o.a.g.tunnel.TunnelRequestService - User "natrayan" connected to connection "1".
    01:52:10.739 [http-nio-8080-exec-9] INFO o.a.g.tunnel.TunnelRequestService - User "natrayan" disconnected from connection "1". Duration: 46 milliseconds
    01:52:26.690 [http-nio-8080-exec-6] INFO o.a.g.tunnel.TunnelRequestService - User "natrayan" connected to connection "1".
    01:52:26.739 [http-nio-8080-exec-10] INFO o.a.g.tunnel.TunnelRequestService - User "natrayan" disconnected from connection "1". Duration: 49 milliseconds
    01:52:42.691 [http-nio-8080-exec-1] INFO o.a.g.tunnel.TunnelRequestService - User "natrayan" connected to connection "1".
    01:52:42.717 [http-nio-8080-exec-3] WARN o.a.g.s.GuacamoleHTTPTunnelServlet - HTTP tunnel request rejected: Cannot connect. Connection already in use by this user.
    01:52:42.731 [Thread-62] INFO o.a.g.tunnel.TunnelRequestService - User "natrayan" disconnected from connection "1". Duration: 39 milliseconds
    02:04:06.129 [http-nio-8080-exec-10] INFO o.a.g.tunnel.TunnelRequestService - User "natrayan" connected to connection "1".
    02:04:06.179 [http-nio-8080-exec-3] INFO o.a.g.tunnel.TunnelRequestService - User "natrayan" disconnected from connection "1". Duration: 49 milliseconds



  • @aaronstuder said in Guacamole on Fedora 27:

    I’ll try this again tomorrow

    And the verdict was?



  • @aaronstuder said in Guacamole on Fedora 27:

    Installing Docker as Described Here:

    https://docs.docker.com/install/linux/docker-ce/fedora/

    Any reason you went with the Docker third party repos instead of letting Fedora manage it?



  • @scottalanmiller Fedora was too old of date at the time.



  • @net-runner said in Guacamole on Fedora 27:

    I've tried Guacamole on CentOS and Debian. Both worked fine, but it was a bare-metal install (not docker). Check Guacamole and Tomcat logs to identify if they are running at all and try to see your connection attempts there. If there is nothing it has to be firewall/connectivity issue.

    The Docker instructions don't seem to work, which seems to be my experience with all Docker instructions. Sounds like it'll be easy, but never "just works" and takes more complicated fiddling than just doing traditional installs.


Log in to reply