Dedicated IP VirtualHosts from httpd.conf

D

dreamscape

Active Member
#1
#1
I've been thinking about using LiteSpeed on my production server which is cPanel controlled. I love the use Apache config option, but when I test it locally, it lumps all my SSL hosts under a single *:443 listener. Obviously this is no good as each SSL host needs a dedicated IP. They are setup under dedicated IPs in httpd.conf.

Is this a known issue, or could it just be how I have my local SSL hosts set up?

Come to think of it, it also lumped all the non SSL hosts together under a single *:80 even though some are setup on dedicated IPs in httpd.conf.

Can anyone running LiteSpeed on cPanel using the read Apache config option comment on if LiteSpeed sets up appropriate listeners for hosts with dedicated IPs, or if it tries to lump them all together under the wildcard as it is doing for me locally?

Thanks
 
D

dreamscape

Active Member
#2
#2
Ok so I setup litespeed on the server and setup "Using Apache Configuration File" with a port offset to test it out.

The same thing happens with a standard cPanel httpd.conf, all dedicated IP virtual hosts are lumped together under the wildcard * with the shared-IP virtual hosts.

So I guess LiteSpeed does not support dedicated IP virtual hosts when using the "Using Apache Configuration File" option?
 
D

dreamscape

Active Member
#4
#4
Sure. I just emailed a portion of the httpd.conf over.

The SSL certificates are not working either. If I try to connect to one of the SSL hosts using curl to see the error, I get the message "unknown protocol". The certificates were all setup & installed through WHM, so the keys and everything were generated by cPanel, if that helps any.
 
C

chernann

Member
#5
#5
Same problem as dreamscape. Virtualhosts with dedicated ips and SSL certs are not being set up correctly when loading Apache config as created by Cpanel. FYI, Cpanel restricts the cert and private (key) directory to root group only.
 
M

mistwang

LiteSpeed Staff
#6
#6
Cpanel uses a global listener for all SSL vhosts, whereas LiteSpeed needs individual listener for each SSL vhost, we need a little time to come up with a clean solution for this.

Please stay tuned. :)
 
R

Rob T

Member
#10
#10
Did this fix also take care of assignment of non-ssl dedicated ips as well, or is it just fixing SSL? All sites seem to be lumped in to one listener even if they are assigned to a dedicated ip in the apache httpd.conf under cpanel, but I have several customers who have dedicated IP sites that are not ssl.
 
R

Rob T

Member
#12
#12
Actually, I think I figured it out - by default, cpanel's vhost template looks something like this for a site with a dedicated ip address:

<VirtualHost xx.46.147.3:80>

Litespeed would not answer requests for the site in question that way. Once I changed the directive to look like this:

<VirtualHost xx.46.147.3>

It seems to work fine. The only issue is that while the site works ok as long as it's called using the URL, if you call it in a web browser using just the IP address you still get a default cpanel page rather than the site bound to that IP. Anyone know of a fix for that so the site can be called using it's URL or the IP address directly?
 
You must log in or register to reply here.
Top