I figured out taht my 'not authorized' problems are from folks behind more restricive firewalls that block port 5229. Is there any way to change this in the server? I see how to do it in the index.html file...
Guess there's no answer for this. Is there anyway to disable this port 5229 lookup? If a web based client still has to have ports opened up in a firewall, there's no real advantage to using the web client, no?
You need to open port 5229 on server side, not on client side. Anyway this solved my "not authorized" problems.
You can get around this by using http connections instead of socket, but performance is significantly better for socket.
But, don't you have to still open a port for http? Certain site that users are at have very restrictive egress filtering, so I need to find a way to make this work. I tried jwchat, but that just doesn't seem to work with openfire 3.5.1.
You could use Apache's ProxyPass/ProxyPassReverse functionality to "forward" the http binding path from port 80 to the http binding port.
OK, maybe I'm being a little dense. This is a Flash applet. It tries to get the .xml config file from the server. Can it be served by the same port 80 webserver, or does it have to be on another port? I have users that are behind very restrictive firewalls, with aggressive egress filtering. This is what I have:
I've got the same problem here : I'd prefer to do not open a new port and use the http URL but that doesn't work :/.
Is it working for someone ?
Retrieving data ...