[
https://issues.apache.org/jira/browse/GUACAMOLE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088885#comment-16088885
]
AlanBaban2000 commented on GUACAMOLE-283:
-----------------------------------------
I see, that's what I am trying to investigate as well.
At the moment I have issue of blank page when load balances. Would probably
think of session aggregation between the instances.
However I am not using NGinx as frontend. Is it straight forward? Would you
please share the config, and where does it sit on the network? Is it running on
Ubuntu?
I will share my findings as we progress
> HA in Guacamole
> ---------------
>
> Key: GUACAMOLE-283
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-283
> Project: Guacamole
> Issue Type: New Feature
> Components: guacamole-client, guacamole-server
> Affects Versions: 0.9.12-incubating
> Reporter: Thiago dos Santos Nunes
>
> A great feature for guacamole would be high availability both on the client
> (mainly) and on the server.
> In the client the ideal would be to be able to at least be able to block by
> the number of simultaneous connections even having an environment with
> several vms or containers.
> I currently have an environment with 3 guacamole servers with Tomcat 8
> running behind a HAPROXY. But I lose the block by simultaneous connection (I
> charge my clients for simultaneous connection) and I can not give up having
> more than one vm, because if one falls I lose all. It would also be great if
> the user does not need to log in again if they go to another server (session
> permanence). Today I work with hundreds of simultaneous users from different
> places.
> It would also be very good to be able to separate the client from the server
> and be able to work on HA on the server as well.
> My Environment:
> 3x Guacamole server and client: 0.9.12
> Database and Authentication: MySQL (another vm)
> File Server: SFTP (another vm)
> I alread commented this on:
> https://issues.apache.org/jira/browse/GUACAMOLE-189
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
