powered by Jive Software

Red5 Error findings

I did a bit testing as I like the Red5 plugin. Server Wildfire 3.2 latest red5 plugin browser based testing

  1. using the standard port 9090 the server domain is correct entered into the server field in the login screen

  2. using the secured port 9091 the server domain is shown as localhost, NOT the correct domain.

the following tests are done with port 9090 to have a small correct footprint

  1. the search facility is not working. propably an “localhost” issue

  2. groupchat: opening the groupchat window and just clicking ‘‘cancel’’ will open up the chat window instead of closing the window. As well in this first window, the domain is set to ‘‘localhost’’ instead of the correct domain.

  3. for the search of groupchat the same, conference.localhost

  4. the search for the groupchat seems to work, IF the search is changed to conference.domainofserver

here a snippet of the warn-log


2007.02.15 22:27:37 Closing session due to incorrect hostname in stream header. Host: localhost. Connection: org.jivesoftware.wildfire.net.SocketConnection@e86a5f socket: Socket[addr=/127.0.0.1,port=2214,localport=5269] session: null

2007.02.15 22:30:33 Closing session due to incorrect hostname in stream header. Host: localhost. Connection: org.jivesoftware.wildfire.net.SocketConnection@18c28a socket: Socket[addr=/127.0.0.1,port=2331,localport=5269] session: null

2007.02.15 22:30:55 Closing session due to incorrect hostname in stream header. Host: localhost. Connection: org.jivesoftware.wildfire.net.SocketConnection@373a9c socket: Socket[addr=/127.0.0.1,port=2347,localport=5269] session: null

2007.02.15 22:53:21 Closing session due to incorrect hostname in stream header. Host: localhost. Connection: org.jivesoftware.wildfire.net.SocketConnection@326c98 socket: Socket[addr=/127.0.0.1,port=3314,localport=5269] session: null

2007.02.15 22:53:23 Closing session due to incorrect hostname in stream header. Host: localhost. Connection: org.jivesoftware.wildfire.net.SocketConnection@3d0426 socket: Socket[addr=/127.0.0.1,port=3317,localport=5269] session: null

2007.02.15 22:56:48 Client provided invalid session: 744e13c5.

2007.02.15 22:56:48 Closing session due to incorrect hostname in stream header. Host: localhost. Connection: org.jivesoftware.wildfire.net.SocketConnection@235551 socket: Socket[addr=/127.0.0.1,port=3505,localport=5269] session: null

2007.02.15 22:56:50 Client provided invalid session: 744e13c5.

2007.02.15 22:56:51 Client provided invalid session: 744e13c5.

2007.02.15 22:56:52 Client provided invalid session: 744e13c5.

2007.02.15 22:56:53 Client provided invalid session: 744e13c5.

2007.02.15 22:56:54 Client provided invalid session: 744e13c5.

2007.02.15 22:56:56 Client provided invalid session: 744e13c5.

2007.02.15 22:56:57 Client provided invalid session: 744e13c5.

2007.02.15 22:56:58 Client provided invalid session: 744e13c5.

2007.02.15 22:56:59 Client provided invalid session: 744e13c5.

2007.02.15 22:57:01 Client provided invalid session: 744e13c5.


a snipped of the info log


2007.02.15 21:00:39 Multi User Chat domain: conference.jabber.ca

2007.02.15 21:00:39 Publish-Subscribe domain: pubsub.jabber.ca

2007.02.15 21:00:39 Started server (unencrypted) socket on port: 5269

2007.02.15 21:00:40 Started plain (unencrypted) socket on port: 5222

2007.02.15 21:00:46 Started SSL (encrypted) socket on port: 5223

2007.02.15 21:00:55 Wildfire 3.2.0

2007.02.15 21:00:59 Admin console listening at:

http://jabber.ca:9090

https://jabber.ca:9091

2007.02.15 21:01:01 Starting transport service: msn

2007.02.15 21:01:02 Initializing Red5 Plugin

2007.02.15 21:01:02 Registering Red5 plugin as a component

2007.02.15 21:01:02 Starting red5

2007.02.15 21:15:05 Registering Red5 plugin as a component

2007.02.15 22:22:13 Multi User Chat domain: conference.jabber.ca

2007.02.15 22:22:14 Publish-Subscribe domain: pubsub.jabber.ca

2007.02.15 22:22:14 Started server (unencrypted) socket on port: 5269

2007.02.15 22:22:14 Started plain (unencrypted) socket on port: 5222

2007.02.15 22:22:18 Started SSL (encrypted) socket on port: 5223

2007.02.15 22:22:26 Wildfire 3.2.0


In the info log you can clearly see the domain set to jabber.ca

PS. A registration at ‘‘localhost’’ was possible. Haven’'t tested further yet.

turbo

Hi turbo,

Thanks for the testing and feedback. I am currently working on the next release 0.0.4 so this will help a lot.

I am trying to fix as many JWChat and Wildfire compatibility issues as I can, so please keep on testing and posting.

-dele

Dele,

will do. Like the plugin so I want to help you guys as much as I can. I find it the best and easiest way to have a web client working.

And the whole purpose: get it working as proper as possible.

turbo

I too have these problems, I also can’'t get JWChat working at all. I think its the fact that my xmpp domain is domain.com and my wildfire server is im.domain.com. When I go to http://im.domain.com:9090/red5/ it populates the names with im.domain.com instead of domain.com .

keithconger,

I am using the http address with the domain the jabber server is running on. I don’'t have any log-in problems.

The user names should be populated with user@jabber server domain and not with the other domain.

By the way, your wildfire server domain should be in fact your xmpp domain. And how is your DNS setup ? Do you have at all an A (host) record for domain.com ? If not, it will bring you nowhere.

turbo

I cannot seem to get Red5’'s JWChat5 to work with Wildfire 3.2.1 …

Is this a known issue yet?

I get “Service Unavailable” when attempting to log in on JWChat5.

I have just upgraded to Wildfire version 3.2.1 and JWChat5 works for me.

I am however running the next version of Red5 Plugin 0.0.4 which is still in development. If this is a show stopper for anyone, please let me know and I will investigate.

-dele

Message was edited by: dele