You don't mention if you changed your version of Openssl in installing mod-ssl, which I suspect you did. If so, that can stop stunnel working as it is usually linked against a specific version of either SSLeay (is anyone actually using that anymore?) or Openssl. I had this problem for a while till I recompiled stunnel against the source tree of the same version of Openssl. Check your syslog for a definitive answer as stunnel should be logging any failures there. I use stunnel for SWAT and mod_ssl on the same machines without any problems. - John Airey Internet Systems Support Officer, ITCSD, Royal National Institute for the Blind, Bakewell Road, Peterborough PE2 6XU, Tel.: +44 (0) 1733 375299 Fax: +44 (0) 1733 370848 [EMAIL PROTECTED] -----Original Message----- From: RCURTIS [mailto:[EMAIL PROTECTED]] Sent: 01 November 2000 01:45 To: '[EMAIL PROTECTED]' Subject: after install of mod-ssl, stunnel broken I have been using stunnel on an apache 1.3 webserver to connect to the web interface of SAMBA called SWAT.� After install of mod-ssl, I cannot connect via https: to SWAT i.e.� https://xxx.xxx.xxx.xxx:901 <https://xxx.xxx.xxx.xxx:901> ���� If connecting to swat outside stunnel, all works fine.� Any ideas as to what the mod-ssl install changed or how to make it so that I can continue to use stunnel to connect while at the same time using mod-ssl on the web server?� Any help appreciated ..�� Thanks! � Richard Curtis [EMAIL PROTECTED] � ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
