From: <kl...@hy...> - 2004-08-02 09:05:15
|
2004-08-02 kl. 04.23 skrev duf...@pi...: > Hello, I've just set up yaws and I'm having a problem with the ssl > server. The logs don't report any errors, but when I try to go to the > https site, the connection times out. The normal http works fine, > netstat reports that it's listening on port 443. > > # tail /var/log/yaws/report.log > =INFO REPORT==== 1-Aug-2004::14:41:29 === > Yaws: Listening to 0.0.0.0:443 for servers > - https://pizzaz under /var/yaws/www/secure > > =INFO REPORT==== 1-Aug-2004::14:41:29 === > Yaws: Listening to 0.0.0.0:80 for servers > - http://pizzaz under /var/yaws/www/insecure > Looks good, > =INFO REPORT==== 1-Aug-2004::14:41:29 === > Changed uid to 65534 > I've possibly never even tried the combination of setuid server and ssl. Maybe there are bugs there. > Here is the server portions of the conf file: > <server pizzaz> > port = 80 > listen = 0.0.0.0 > docroot = /var/yaws/www/insecure > dir_listings = true > tilde_expand = true > </server> > <server pizzaz> > port = 443 > docroot = /var/yaws/www/secure > listen = 0.0.0.0 > dir_listings = true > <ssl> > keyfile = /var/yaws/yaws-key.pem > certfile = /var/yaws/yaws-cert.pem > </ssl> > </server> > Config looks jus fine. One common error with yaws and ssl is that the the erlang installation didn't do a proper install of ssl. Try to type > ssl:start(). into the erlang shell and make sure ssl is properly running. > The computer is running linux 2.6.7, OTP R9C-2. > Which very very close to the system I'm running myself. /klacke |