virtual_host2_secure.conf isn't parsed while SSL=1 and CGI=1

R

rsdrsd

Verified User
Joined
Jan 12, 2013
Messages
10
I want to use https for an admin area. On another server I see in custom httpd confs the virtualhosts for port 443, but for the server where I want to create an admin area for I don't see the virtual hosts for port 443. I have searched the internet and this forum, but I can't find anything. I am running Directadmin 1.42.1. I saved the custom httpd confs many times, but the 443 virtualhosts won't appear. On the other server I can see them. What can be wrong? I just looks like that virtual_host2_secure.conf isn't parsed.

A while ago I moved this site to this server. Everything is working fine, except the virtualhosts for 443. And I have SSL enabled for the domain.
 
I think i've found it

In /etc/httpd/conf/extra on the good working server I have:


httpd-directories.conf -> httpd-directories-new.conf

and on the one where it isn't working I have:

httpd-directories.conf -> httpd-directories-old.conf

What is this and why is there a difference?
 
My own admin area. I want to run it in the private_html folder.

When I look at custom httpd configurations and then the contents of httpd.conf. There is nothing with the 443 port in it. Really annoying, while on my other servers it is.

I just added secure_htaccess=yes and harden-symlinks-patch=yes and I rewrote all httpd.conf , but nothing is changed... just made a symlink to httpd-directories-new.conf also, nothing is changed, the host2_secure.conf still isn't parssed.
 
When I go to https://www.doamin.com I see the message: Apache is functioning normally! and not the message for private_html/. This is because the virtual_host2_secure.conf isn't parsed!
 
The problem is:

in /usr/local/directadmin/data/users/username the <VirtualHost ip:443 > isn't available. But how to fix it, while SSL=1 and CGI=1 ?
 
You must log in or register to reply here.
Back
Top