HipChat Server 2.0.5 video seems to redirect traffic to id.google.com and then to hipchat.com, before rejecting anyone's attempt at creating a video session. The error is "Sorry, you are not allowed to join this call."

[DanielF · Accepted solution]

The issue turned out to be a edge case for the HipChat client: you have to sign out, then "forget this account," then log back in again to get hipchat.com to change to hipchat.me for the video links. Turns out it has nothing to do with id.google.com or anything else.

[wdehaan]

And we have a fix in for HCS build 2.0.6. Thanks so much!

[DanielF]

grep video_base_url /etc/chef/solo.json /hipchat/config/site.json
/etc/chef/solo.json: "video_base_url": "https://hipchat.me",
/hipchat/config/site.json: "video_base_url": "https://hipchat.me",

As you suggested.

I've got a support ticket open now that we're actively working on. Thanks for your insight.

[wdehaan]

Can you verify the video endpoint is set on HCS? 

$ grep video_base_url /etc/chef/solo.json /hipchat/config/site.json
/etc/chef/solo.json: "video_base_url": "https://hipchat.me",
/hipchat/config/site.json: "video_base_url": "https://hipchat.me",

If you don't see a match to the above output please run: hipchat video --url "https://hipchat.me"

This is puzzling. Do send a note to server-support@hipchat.com if you haven't already. Support staff will be online Monday globally.

[DanielF]

Of note, only the owner user can create HipChat Video rooms using he https://hipchat.me servers whereas all other users—even from the same host and client—use https://hipchat.com, which fails.

[DanielF]

Seems to be fine: we get:

admin@hipchat:~$ hipchat video --checkkeyserver
Successfully communicated with https://video.hipchatserver.com
Successfully saved video key to https://video.hipchatserver.com as 2d5b88c796a8db7cd8aca33aab7fd0d8980c280c64411fb35258fbda4cac0702
Updated the video configuration
Updating system configuration, this may take a few minutes...
run-parts: /home/admin/startup_scripts/disable_retention_purger exited with return code 1
Restarting services (apps only)

[wdehaan]

Forgive me for the basic troubleshooting in the answers forum..

Clients have to be restarted to be able to participate. If that fails please try to logout and back in.

As a point of reference, does the web chat client work with the new video calls?

[DanielF]

Clients were restarted, brought up to date to 2.48, but no luck with them. However, at your suggestion I tried out the WebUI and, sure enough, the correct hipchat.me URL was generated I got it. Now how to propagate whatever changes need to be made for all the users.

[wdehaan]

Hi @Daniel Finkelstein,

Thank you for jumping on the beta release!

HipChat Server has to register with the video service to establish a trust (based on a combination of a public/private key and the HCS license)

Please SSH into the HCS install and run: 

hipchat video --checkkeyserver

It should pick up the outbound proxy config if you have that set.

[Alexander Hall]

So the new video chat/conferencing (with jitsi-meet DNA) will only work with a internet connection?

[wdehaan]

HipChat Server only needs to register once, then the clients do need network connectivity for HipChat Video. We're looking at fully on-premise video (since it's common DNA, indeed) using Jitsi-Meet installations, as in https://jitsi.org/Main/Download