Hi Chris,<br><br>Thanks for the pointers. As I am using Jabberd version 1.4.4, the jabber.xml contents seemed different from what you have provided. Nonetheless, I followed closely to what you have suggested (creating a self-signed cert and linking it in the jabber.xml) and managed to get Pidgin to connect to my Jabber Server on port 5223.<br>
<br>I am now faced with another issue that hopefully you can shed some light on:<br><br>In my VenueServer.cfg, the text port I am connecting to is 5223. However, when I create add new venues through the Venue Management tool, a new chat room is NOT created on the Jabber end.<br>
<br>Please advise.<br><br>Thanks<br>Cheers<br>lest<br><br><br><br><br><br><div class="gmail_quote">On Sat, Jun 14, 2008 at 12:12 PM, Christoph Willing <<a href="mailto:c.willing@uq.edu.au">c.willing@uq.edu.au</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
On 14/06/2008, at 12:02 AM, lester leong wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi All,<br>
<br>
Like Luis, I managed to set up Jabber Server ( Jabberd-1.4.4) and edited the VenueServer.cfg file. However, when I launch the Venue Client and join a venue, I get the following error:<br>
</blockquote></div>
[snip]<div class="Ih2E3d"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
File "/usr/lib/python2.4/site-packages/gov/lbl/dsd/bajjer/ssl.py", line 112, in send<br>
bytes = self._ssl.send(data)<br>
Error: [('SSL routines', 'SSL23_GET_SERVER_HELLO', 'unknown protocol')]<br>
</blockquote>
<br>
<br></div>
Lester,<br>
<br>
This error may be due to incorrect jabber server certificate configuration (or possibly the certificate itself). To work with the VenueClient correctly, the jabber server needs an SSL certificate (not necessarily and AG certificate).<br>
<br>
The jabber.xml configuration file needs to include the location of the certificate and it also needs to correct entries to tell the jabber server how to use it - there are two areas in the jabber.xml file that need attention:<br>
<br>
1. in the c2s (client to server) service area, you'll need an uncommented line with:<br>
<tls port='5223'><a href="http://0.0.0.0" target="_blank">0.0.0.0</a></tls><br>
which tells the server to accept input from any external host at port 5223. I mention "uncommented" here because the configuration file is quite cluttered and its easy not to notice that a line is actually commented out and therefore have no effect.<br>
<br>
2. in the tls area, you need to specify the credentials to be used - something like this:<br>
<credentials><br>
<default/><br>
<pem>/etc/jabberd/ssl.pem</pem><br>
</credentials><br>
which tells the server to use the certificate found at /etc/jabberd/ssl.pem<br>
<br>
<br>
One other thing, you may find it easier to use a different jabber client while you're troubleshooting your jabber server. Use something like Pidgin to set up a new account at your server using port 5223. On my Pidgin client there's a checkbox marked "Force old (port 5223) SSL" as well as a "Connect port:" entry in which to insert "5223". If that works, then the VenueClient will work.<br>
<br>
<br>
chris<br><font color="#888888">
<br>
<br>
Christoph Willing +617 3365 8350<br>
QCIF Access Grid Manager<br>
University of Queensland<br>
<br>
<br>
<br>
<br>
</font></blockquote></div><br>