PDA

View Full Version : Suggestions for new beta custombuild



akukula
05-23-2007, 03:14 PM
Hello,

I was performing Apache 1.3 and PHP 4 upgrade to Apache 2.2 and PHP 5.2.2. Here are suggestions and a help request.

1) On FreeBSD 6.2 the ./build script should check/add the following line to /boot/loader.conf:
accf_http_load="YES"
and do:
kldload accf_http
while upgrading or else there will be error upon starting httpd:
[Wed May 23 23:15:53 2007] [warn] (2)No such file or directory: Failed to enable the 'httpready' Accept Filter

2) it turned out that the zziplib-0.10.82 downloaded by ./build update_data doesn't compile on FreeBSD 6.2 because the file zzip/zzip.h lacks the following line:
#include <sys/types.h>
fortunately I had previously downloaded sources of the same version that did contain that line.

And now real problem (not related to ./build but rather to Apache 2.2 configuration in DA) in which I need your help:

3) there's a problem with VirtualHost and SSL in Apache 2.2, there are many lines in /var/log/httpd/error.log similar to the following, one per virtual host

[Wed May 23 23:16:44 2007] [warn] Init: SSL server IP/port conflict: www.domain.tld:443 (/usr/local/directadmin/data/users/user1/httpd.conf:41) vs. www.domain2.tld:443 (/usr/local/directadmin/data/users/user2/httpd.conf:41)
[Wed May 23 23:16:44 2007] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!

Please help solve that problem, as there are some customers that would want to use https:// with their webpages.

Thanks and regards,
Andrzej Kukula

nobaloney
05-23-2007, 07:11 PM
There's actually a problem with SSL and virtual hosts in every version of apache, and it's caused by a limitation of the ssl protocol. If the errors don't occur in earlier versions of apache then the problem has to be in configuring which errors get written to a log; you shouldn't be using https with shared IP#s, and in fact DirectAdmin shouldn't be allowing you to turn on https with shared IP#s.

So what am I missing?

Jeff

m4ri00sh
06-14-2007, 08:52 PM
Actually, I got the same problem ....
"You should not use name-based virtual hosts in conjunction with SSL"

hmmmm ... ?:confused:

nobaloney
06-17-2007, 10:25 AM
Actually, I got the same problem ....
"You should not use name-based virtual hosts in conjunction with SSL"
This is what you should get. Because SSL Certificates don't work with name-based hosting. As I wrote, the limitation is with the Certificate itself.

Jeff