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

Thiago dos Santos Nunes commented on GUACAMOLE-283:
---------------------------------------------------

My HAProxy is on Pfsense firewall.

 Automaticaly generated, dont edit manually.
# Generated on: 2017-05-15 00:05
global
        maxconn                 10000
        stats socket /tmp/haproxy.socket level admin
        uid                     80
        gid                     80
        nbproc                  1
        chroot                  /tmp/haproxy_chroot
        daemon
        server-state-file /tmp/haproxy_server_state

listen HAProxyLocalStats
        bind 127.0.0.1:2200 name localstats
        mode http
        stats enable
        stats refresh 30
        stats admin if TRUE
        stats uri /haproxy/haproxy_stats.php?haproxystats=1
        timeout client 5000
        timeout connect 5000
        timeout server 5000

frontend App1-Azure
        bind                    MYIP:8080 name MYIP:8080   
        mode                    http
        log                     global
        option                  dontlog-normal
        option                  http-server-close
        option                  forwardfor
        acl https ssl_fc
        http-request set-header         X-Forwarded-Proto http if !https
        http-request set-header         X-Forwarded-Proto https if https
        maxconn                 10000
        timeout client          30000
        default_backend BackendApp1Azure_http_ipvANY

backend BackendApp1Azure_http_ipvANY
        mode                    http
        log                     global
        stats                   enable
        stats                   uri /haproxy?stats
        stats                   realm .
        balance                 source
        timeout connect         3000000
        timeout server          300000
        retries                 3
        fullconn 2000
        server                  App_DR_3_IP_15 192.168.33.15:8080 check inter 
2000  weight 2 
        server                  App_DR_2_IP_4 192.168.33.4:8080 check inter 
2000  weight 2 
        server                  App_DR_1_IP_7 192.168.33.7:8080 check inter 
2000  weight 2

> 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)

Reply via email to