Openfire and Ijab

Openfire Openfire Support
1

I’ve read through countless posts on this subject and none seem to solve my problems.

I have openfire running on a VPS. A cname is being used for msg.mydomain.tld (the real domain is unrelated to what I want the openfire address to be) which houses the openfire server which is also an apache2 (ubuntu) install. Openfire runs well when connecting using a system like Pidgin.

Ijab is hosted on im.mydomain.tld which is standard hosting account. Nothing special. However, when I try to connect with ijab it never seems to finish and just keeps loading.

Below is my ijab_config.js file (The important parts).

    domain:"im.mydomain.tld",         http_bind:"http://msg.mydomain.tld:7070/http-bind/",         host:"msg.mydomain.tld",         port: 5222,         server_type:"openfire",

The ports are correct according to the openfire admin panel and http-bind is enabled. So what am I doing wrong? Accessing HTTP bind directly gives me a 400 error which I’m assuming is because I’m access it from a browser and not the client.

Some posts mentioned about .htaccess modifications in apache, however, I did not think this was applicable because I’m linking directly to it and not simply pointing to /http-bind/

Community help will be greatly appreciated. I hope I provided enough details.

2

Are you able to access http://msg.mydomain.tld:7070/http-bind/ ?

If not, check your machine to see if it’s allowing connections to that port, if openfire is running and http-bind has been enabled on that port, it should allow you to connect to it. Doing a telnet to the port should show you if the port is open. If it is, then it’s a problem with your iJab config and you probably will need the .htaccess url rewrite rules in place.

3

It is accessble. As I said above, “Accessing HTTP bind directly gives me a 400 error which I’m assuming is because I’m access it from a browser and not the client” Jetty shows it, but with an error.

I’m not exacally sure how the .htaccess rewrite rules apply in this case since the /http-bind/ shows up out of the box. Why exacally does this have anything to do with apache?

4

SirMoo,

Because the loaded javascript has to call back to the same server IP and network port address that it was loaded from (your apache server).

daryl