Skip to content
This repository has been archived by the owner on Jun 30, 2022. It is now read-only.

muc_domain depreciated for private hipchat server? #36

Open
IAmPatrickB opened this issue Feb 11, 2016 · 3 comments
Open

muc_domain depreciated for private hipchat server? #36

IAmPatrickB opened this issue Feb 11, 2016 · 3 comments

Comments

@IAmPatrickB
Copy link

The readme indicates muc_domain is depreciated, however I believe it is still required for private servers. Without it, as ours is not conf.hipchat.com, I receive a 400 during connection. When I set it in config, however, I do not receive a 400:

<error code='400' type='modify'><bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error>

I'm still working on getting this up and running, but wanted to document this for anyone else running into the same issue.

@IAmPatrickB
Copy link
Author

Update: Setting the muc_domain was all that is required for private server, but it would not respond to private messages. Once I specified a room as part of the config as well, it is able to successfully connect to the room and respond to commands.

@jimmycuadra
Copy link
Collaborator

The way it's written in the README is a bit confusing—it's only the rooms setting that is deprecated, not all the bullet points below that. If you want to revise the formatting of the README to make that more clear, a PR would be welcome.

@IAmPatrickB
Copy link
Author

Sounds good, I'd be happy to contribute.

Thanks for the response!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants