- ubuntu 10.04
- ejabberd 2.1.9
- JWChat (don't know what version)
- NXB 0.5.0
I'm using mod_proxy to get to NXB and to http-bind.
Tried the following
- Straight JWChat to http-bind on ejabberd: worked
- JWChat to NXB: failed
- Web browser to NXB: failed
- Pointed the URL for NXB to http-bind via apache: failed
That last one makes me wonder what the heck is going on. I tried poking around and finally discovered that I was using the wrong setup with JWChat. Used the right setup and I was able to set the NXB url to http-bind and it worked.
I then tried pointing the apache proxy back to NXB and it worked. Go me!
I shut down NXB and tried again. It still worked. This means that I was still using the http-bind proxy instead of the NXB proxy. Nuts. After a bit of poking around, I discovered that I was using the wrong option for JWChat. Sheepish grin.
Changed the option in JWChat to NXB and tried again. It failed. Yays! Erm, I mean, er...yeah, behaved as expected. Yeah, that's it.
Started up NXB again and tried JWChat. Failed with "service unavailable." Hrm...
Tried disabling the NXB proxy and going to a test page. That worked. Hrm...
Tried going directly to NXB instead of through the proxy. That worked --- the problem has to do with apache/proxy not with NXB.
After a bit of mucking about doing google searches came up with the following cause: I needed to create a <proxy> statement in my proxy.conf file. The stanza looks like this:
<proxy http://localhost:8888/http-bind>
Order allow,deny
Allow from all
</proxy>
Mind you, this was only after thrashing about for a long while...sigh.
OK, so I tried going to NXB again through JWChat. It got through --- yays! Then NXB promptly complained about not having some node module called "semver." Nuts. Installed that and tried again. Now NXB spews lots of messages that make me think it's doing something, but still no login from JWChat. Could it be that NXB does not know which server to go to. Hmmmm....
Looked in the copious messages that NXB was producing and they seemed to indicate that NXB was able to talk to ejabberd. Tried logging onto regular old XMPP (port 5222) with Pidgin and that worked as well. A regular login through ejabberd's http-bind showed that users could see each other.
Tried logging in via ejabberd/http-bind through Pidgin but that failed. Mucked about for a bit and discovered that Pidgin is very sensitive when it comes to the BOSH URL for such an account. Specifically,
http://foobar/http-bind/
Will not work, but
http://foobar/http-bind
Works correctly. Don't you just love computers? I know I do.
Tried logging in via Pidgin through the proxy. That failed. Tried the same thing only this time going directly to the NXB URL. That worked. Tried logging in via JWChat and the proxy. That failed: even with variations on the connection URL.
OK, given all the joy that I was getting by going through apache I am going to stop trying to make apache work for the time being.
I shut down NXB and tried again. It still worked. This means that I was still using the http-bind proxy instead of the NXB proxy. Nuts. After a bit of poking around, I discovered that I was using the wrong option for JWChat. Sheepish grin.
Changed the option in JWChat to NXB and tried again. It failed. Yays! Erm, I mean, er...yeah, behaved as expected. Yeah, that's it.
Started up NXB again and tried JWChat. Failed with "service unavailable." Hrm...
Tried disabling the NXB proxy and going to a test page. That worked. Hrm...
Tried going directly to NXB instead of through the proxy. That worked --- the problem has to do with apache/proxy not with NXB.
After a bit of mucking about doing google searches came up with the following cause: I needed to create a <proxy> statement in my proxy.conf file. The stanza looks like this:
<proxy http://localhost:8888/http-bind>
Order allow,deny
Allow from all
</proxy>
Mind you, this was only after thrashing about for a long while...sigh.
OK, so I tried going to NXB again through JWChat. It got through --- yays! Then NXB promptly complained about not having some node module called "semver." Nuts. Installed that and tried again. Now NXB spews lots of messages that make me think it's doing something, but still no login from JWChat. Could it be that NXB does not know which server to go to. Hmmmm....
Looked in the copious messages that NXB was producing and they seemed to indicate that NXB was able to talk to ejabberd. Tried logging onto regular old XMPP (port 5222) with Pidgin and that worked as well. A regular login through ejabberd's http-bind showed that users could see each other.
Tried logging in via ejabberd/http-bind through Pidgin but that failed. Mucked about for a bit and discovered that Pidgin is very sensitive when it comes to the BOSH URL for such an account. Specifically,
http://foobar/http-bind/
Will not work, but
http://foobar/http-bind
Works correctly. Don't you just love computers? I know I do.
Tried logging in via Pidgin through the proxy. That failed. Tried the same thing only this time going directly to the NXB URL. That worked. Tried logging in via JWChat and the proxy. That failed: even with variations on the connection URL.
OK, given all the joy that I was getting by going through apache I am going to stop trying to make apache work for the time being.
No comments:
Post a Comment