Listener Won't Start With SSL or STARTTLS

This is a new install of 1.0.0.2 from the binary installer. It is running on Fedora Core 4. ejabberd runs well until i uncomment the ssl or STARTTLS lines in the ejabberd.cfg. With either of those enabled the listener won't start. I created a cert, removed the passphrase and added the explicit path to the .cfg. I don't see any errors in the ejabberd log or in /var/log/messages.

Here is my cfg with STARTTLS enabled:

% Listened ports:
{listen, [{5222, ejabberd_c2s, [{access, c2s},
{shaper, c2s_shaper}]},
%% Use this line to enable SSL:
%%{5223, ejabberd_c2s, [{access, c2s}, ssl, {certfile, "/home/jabber/conf/ssl.pem"}]},
%%{5223, ejabberd_c2s, [{access, c2s}, ssl, {certfile, "/home/jabber/conf/ssl.pem"}]},

%% Use those lines instead for TLS support:
{5222, ejabberd_c2s, [{access, c2s}, {shaper, c2s_shaper},
starttls, {certfile, "/home/jabber/conf/ssl.pem"}]},
{5223, ejabberd_c2s, [{access, c2s},
tls, {certfile, "/home/jabber/conf/ssl.pem"}]},

Here is my cert (I also tried other permissions and ownership):

[jabber@svoboda conf]$ ls -lh ssl.pem
-r-------- 1 root root 2.3K Dec 28 14:29 ssl.pem

Here is the output of lsof -i for each case:

No SSL:

COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME

epmd 3889 jabber 3u IPv4 40666 TCP *:4369 (LISTEN)
epmd 3889 jabber 5u IPv4 40706 TCP svoboda.bidmc.harvard.edu:4369->svoboda.bidmc.harvard.edu:32798 (ESTABLISHED)
beam 3903 jabber 5u IPv4 40703 TCP *:32797 (LISTEN)
beam 3903 jabber 6u IPv4 40705 TCP svoboda.bidmc.harvard.edu:32798->svoboda.bidmc.harvard.edu:4369 (ESTABLISHED)
beam 3903 jabber 16u IPv4 40728 TCP *:5222 (LISTEN)
beam 3903 jabber 17u IPv4 40730 TCP *:5269 (LISTEN)
beam 3903 jabber 19u IPv4 40732 TCP *:5280 (LISTEN)
ssl_esock 3909 jabber 3u IPv4 40727 TCP svoboda.bidmc.harvard.edu:32801 (LISTEN)

SSL:

COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME

epmd 4137 jabber 3u IPv4 42751 TCP *:4369 (LISTEN)
epmd 4137 jabber 5u IPv4 42791 TCP svoboda.bidmc.harvard.edu:4369->svoboda.bidmc.harvard.edu:32822 (ESTABLISHED)
beam 4151 jabber 5u IPv4 42788 TCP *:32821 (LISTEN)
beam 4151 jabber 6u IPv4 42790 TCP svoboda.bidmc.harvard.edu:32822->svoboda.bidmc.harvard.edu:4369 (ESTABLISHED)
ssl_esock 4157 jabber 3u IPv4 42812 TCP svoboda.bidmc.harvard.edu:32825 (LISTEN)

STARTTLS:

COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME

epmd 4328 jabber 3u IPv4 45299 TCP *:4369 (LISTEN)
epmd 4328 jabber 5u IPv4 45339 TCP svoboda.bidmc.harvard.edu:4369->svoboda.bidmc.harvard.edu:32836 (ESTABLISHED)
beam 4342 jabber 5u IPv4 45336 TCP *:32835 (LISTEN)
beam 4342 jabber 6u IPv4 45338 TCP svoboda.bidmc.harvard.edu:32836->svoboda.bidmc.harvard.edu:4369 (ESTABLISHED)
ssl_esock 4348 jabber 3u IPv4 45360 TCP svoboda.bidmc.harvard.edu:32839 (LISTEN)

I am kind of at a loss here. Am I missing something obvious? Thanks in advance.

While trying to solve my

While trying to solve my problem (see http://www.ejabberd.im/node/566) I seem this behaviour too. Please check if there is no missing or extra "," in your configuration. I've reformatted the config file and using this. Note that there is no "," on the last line inside the port number part.

{5224,
    ejabberd_c2s,
    [ {ip, {83,243,x,x}},
      {access, c2s},
      starttls,
      {certfile, "/home/ejabberd/ssl.pem"}
    ]
},

Thanks. I'm all set now.

Thanks. I'm all set now.

Syndicate content