[AG-DEV] About Text Service

[lester leong]

Hi Chris,

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.

I am now faced with another issue that hopefully you can shed some light on:

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.

Please advise.

Thanks
Cheers
lest





On Sat, Jun 14, 2008 at 12:12 PM, Christoph Willing <c.willing at uq.edu.au>
wrote:

>
> On 14/06/2008, at 12:02 AM, lester leong wrote:
>
>  Hi All,
>>
>> 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:
>>
> [snip]
>
>>
>>  File "/usr/lib/python2.4/site-packages/gov/lbl/dsd/bajjer/ssl.py", line
>> 112, in send
>>    bytes = self._ssl.send(data)
>> Error: [('SSL routines', 'SSL23_GET_SERVER_HELLO', 'unknown protocol')]
>>
>
>
> Lester,
>
> 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).
>
> 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:
>
> 1. in the c2s (client to server) service area, you'll need an uncommented
> line with:
>        <tls port='5223'>0.0.0.0</tls>
> 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.
>
> 2. in the tls area, you need to specify the credentials to be used -
> something like this:
>    <credentials>
>        <default/>
>        <pem>/etc/jabberd/ssl.pem</pem>
>    </credentials>
> which tells the server to use the certificate found at /etc/jabberd/ssl.pem
>
>
> 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.
>
>
> chris
>
>
> Christoph Willing                        +617 3365 8350
> QCIF Access Grid Manager
> University of Queensland
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/ag-dev/attachments/20080614/7ffefdf1/attachment.htm>