(12-02-2014, 09:29 AM)TheVP Wrote: Admin > Sentora Config > ctrl+f > Sentora Apache Port
Also,
Admin > Module Admin > Apache Config > ctrl+f > Apache Port
You have to set the both.
I have Varnish running in front of Apache so that's what I did and it works nicely.
config settings:
Senotoa Apache Port: 80
Module Apache Port: 80
result:
# Configuration for Sentora control panel.
Listen 80
<VirtualHost *:80>
# DOMAIN: test.domain
<virtualhost *:80>
config settings:
Senotoa Apache Port: yy.yy.yy.yy:80
Module Apache Port: xx.xx.xx.xx:80
result:
Listen yy.yy.yy.yy:80
Listen xx.xx.xx.xx:80
# Configuration for Sentora control panel.
<VirtualHost *:yy.yy.yy.yy:80>
# DOMAIN: test.domain
<virtualhost *:xx.xx.xx.xx:80>
As you can see from the second example this does not result in proper virtualhost entires. I used xx.xx.xx.xx and yy.yy.yy.yy in this example just to show what config field results in which output entry. The Problem ist just the leading "*:" in the virtualhost lines.
This means it is possible to change the port the apache server is running on, but not to limit the ip-address to a single ip address. The only solution would be to change the line in the code that creates the virtualhost entry.
Code:
$vhostPort = ( fs_director::CheckForEmptyValue( $rowvhost[ 'vh_custom_port_in' ] ) )
? $VHostDefaultPort
: $rowvhost[ 'vh_custom_port_in' ];
$vhostIp = ( fs_director::CheckForEmptyValue( $rowvhost[ 'vh_custom_ip_vc' ] ) )
? "*"
: $rowvhost[ 'vh_custom_ip_vc' ];
Something like adding a VHostDefaultIP would maybe help here. I could do that changes to the code, but thats inside the core of the application and i am sure future updates would break that again. Any suggestions how to go on?
J