It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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



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:


    mode                    http

    log                     global

    option                  httplog

    option                  dontlognull

    option http-server-close

    option forwardfor       except

    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


        mode tcp

        default_backend hipchart-5222


# round robin balancing between the various backends


backend hipchart-5222

        option tcplog

        mode tcp

        server hc1

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 check verify none ssl


1 answer

0 votes
MB 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.

Max - Premier Support Engineer

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Hipchat

Hipchat Cloud and Stride have reached End of Life (updated)

All good things come to an end - thanks to all our customers and partners who have been along the Hipchat and Stride journey with us.  As of Feb 15th 2019, Hipchat Cloud and Stride have reached ...

35,225 views 9 8
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you