Atlassian Confluence - Synchrony/Collaboration Issues

So we were finally able to get it working, but we ended up separating it out into its own virtual server and DNS URL, even though they both route to the same backend hosts on different ports.

wiki.company.com:443       -> confluence_pool:8090
synchrony.company.com:443  -> confluence_pool:8091

Here is our synchrony VS/POOL config. No iRules, to persistent profile. Just SSL on the client said, plaintext on the server side. Load balancing method round robin. You need to make sure the HTTP profile is applied to the VS so that upgrading connections to web sockets are supported out of the box.

 VS 
ltm virtual vs-wiki-synchrony-443 {
    description "Confluence Synchrony VIP"
    destination 10.10.10.10:443
    ip-protocol tcp
    mask 255.255.255.255
    pool pool-wiki-synchrony-8091
    profiles {
        HTTP-X-Forwarded { }           inherits from HTTP
        clientsslpf_ssl {
            context clientside
        }
        tcp { }
    }
    source 0.0.0.0/0
    source-address-translation {
        type automap
    }
    vs-index 65
}

 POOL 
ltm pool pool-wiki-synchrony-8091 {
    members {
        confluence_node1:8091 {
            address 10.10.10.1
            session monitor-enabled
            state up
        }
        confluence_node2:8091 {
            address 10.10.10.2
            session monitor-enabled
            state up
        }
    }
    monitor gateway_icmp and tcp_half_open
}