XMPP-BOSH not working correctly in Hipchat Data Center? Edited

 

Hi,

Has anyone been able to get XMPP-BOSH (http-bind) working correctly with Hipchat Data Center sitting behind a reverse proxy? Our lita-based bot can authenticate, but can't receive message, nor can it reliably send messages without a delay.

When XMPP-BOSH (http-bind) is tested against Hipchat Server, the bot works perfectly fine authenticating/sending/receiving messages.

We also tried using Adium on Hipchat Data Center and it's experiencing the same issue of not being able to receive messages and the delay in sending messages.

My best guess is that the reverse proxy is doing something strange, we've tried both Haproxy and Nginx, but the issue is still there.

Here is our Haproxy configuration:

defaults

    mode                    http

    log                     global

    option                  httplog

    option                  dontlognull

    option http-server-close

    option forwardfor       except 127.0.0.0/8

    option                  redispatch

    retries                 3

    timeout http-request    10s

    timeout queue           1m

    timeout connect         10s

    timeout client          1m

    timeout server          1m

    timeout http-keep-alive 10s

    timeout check           10s

    maxconn                 3000

 

#---------------------------------------------------------------------

# main frontend which proxys to the backends

#---------------------------------------------------------------------

frontend www

        bind *:80

        default_backend hipchart

        redirect scheme https code 301 if !{ ssl_fc }

frontend www-https

        bind *:443 ssl crt /etc/haproxy/ssl2/

        default_backend hipchart

frontend hipchart-5222

        bind 172.16.65.70:5222

        mode tcp

        default_backend hipchart-5222

#---------------------------------------------------------------------

# round robin balancing between the various backends

#---------------------------------------------------------------------

backend hipchart-5222

        option tcplog

        mode tcp

        server hc1 172.16.65.80:5222

backend hipchart

    option forwardfor

    http-request set-header X-Forwarded-Port %[dst_port]

    http-request add-header X-Forwarded-Proto https if { ssl_fc }

    server  web01 172.16.65.80:443 check verify none ssl

 

1 answer

0 votes
Max Bern Atlassian Team Feb 20, 2018

Hi Hien,

We've discovered a missing XMPP Stanza is not being sent to BOSH clients. A fix is scheduled for a future release, however we do have a workaround for now you can test;

As root on your Datacenter App Nodes perform the following:

  1. Comment Out the following line in /etc/init.d/punjab
  2. #PLUGIN_OPTS="$PLUGIN_OPTS --use_raw"
  3. Restart Punjab "service restart punjab" ( this will cause disruption to connected clients! )

 

Following these changes, the Lita-Hipchat bot or most XMPP-BOSH clients should continue to work as they did in Hipchat Server.

If you continue to experience issues, we'd recommending creating a ticket with our support team.

Cheers,
Max - Premier Support Engineer

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 14, 2018 in Hipchat Cloud

Hipchat Cloud and Stride End of Life: Just over 90 days away

Earlier this year we made the difficult decision to discontinue our team messaging tools, Stride and Hipchat. The end of life date for Stride and Hipchat Cloud is quickly approaching - February 15, 2...

554 views 0 2
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you