webadmin-list

[webmin-l] virtual interface and SSL

[<da...@so...>]

What a wonderful work you guys are doing with webmin, it's power 
continues to grow. Now I don't get into trouble until I experiment with 
undocumented changes ;)

Problem:

In my first attempt to set up SSL virtual websites I failed. Jamie's 
book pointed out that SSL won't work on namebased shared IP. So I 
used Virtualmin to create a virtual IP interface and establish SSL. 
Apache then created another virtual server with port 443 access 
giving two virtual servers ( port 80 and 443) both with the new IP. 
The SSL works great, but port 80 access gives page can't be 
displayed. Mail seems to work fine. I can't find a way to remove the 
virtual Interface from the virtual server and return it to shared as it 
was so that the web at least has access for now.

I then upgraded Virtualmin to 2.610 to no avail. With this exception. 
Now the servers created on Apache show up with a * in the address 
field showing any. I know I shouldn't have experimented on the "live" 
website.

Questions:

--Obviously, why doesn't the port 80 access work?
--How does one remove or change the private IP setting on the 
server? Virtualmin seems to clamp up once it goes private. And 
using network interface module to remove it just shuts the entire 
virtual server down as virtualmin retains the private IP address to 
the server

I'm running Webmin 1.250 and Virtualmin 2.610 on a Slackware 
10.0 server with Apache 1.3.31


thanks for any help,
Dan

Re: [webmin-l] virtual interface and SSL

[Jamie C. <jca...@we...>]

On Sun, 2006-01-29 at 01:55, da...@so... wrote:
> What a wonderful work you guys are doing with webmin, it's power 
> continues to grow. Now I don't get into trouble until I experiment with 
> undocumented changes ;)
> 
> Problem:
> 
> In my first attempt to set up SSL virtual websites I failed. Jamie's 
> book pointed out that SSL won't work on namebased shared IP. So I 
> used Virtualmin to create a virtual IP interface and establish SSL. 
> Apache then created another virtual server with port 443 access 
> giving two virtual servers ( port 80 and 443) both with the new IP. 
> The SSL works great, but port 80 access gives page can't be 
> displayed. Mail seems to work fine. I can't find a way to remove the 
> virtual Interface from the virtual server and return it to shared as it 
> was so that the web at least has access for now.
> 
> I then upgraded Virtualmin to 2.610 to no avail. With this exception. 
> Now the servers created on Apache show up with a * in the address 
> field showing any. I know I shouldn't have experimented on the "live" 
> website.
> 
> Questions:
> 
> --Obviously, why doesn't the port 80 access work?
> --How does one remove or change the private IP setting on the 
> server? Virtualmin seems to clamp up once it goes private. And 
> using network interface module to remove it just shuts the entire 
> virtual server down as virtualmin retains the private IP address to 
> the server
> 
> I'm running Webmin 1.250 and Virtualmin 2.610 on a Slackware 
> 10.0 server with Apache 1.3.31

Port 80 certainly should work, so it is probably best to try to solve
that problem .. especially since Virtualmin cannot yet convert a server
from private IP back to shared.

What exact error message are you getting when you try the port 80 URL?
Or is it just displaying the wrong website? Also, what does the
<Virtualhost> section header look like?

 - Jamie

Re: [webmin-l] virtual interface and SSL

[<da...@so...>]

The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.

   ---- File information -----------
     File:  mod_php_conf.txt
     Date:  23 Feb 2006, 10:34
     Size:  355 bytes.
     Type:  Text

Re: [webmin-l] virtual interface and SSL

[<da...@so...>]

The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.

   ---- File information -----------
     File:  mod_ssl_conf.txt
     Date:  23 Feb 2006, 10:34
     Size:  11377 bytes.
     Type:  Text

Re: [webmin-l] virtual interface and SSL

[<da...@so...>]

To follow up on this I use this quote, " and Junior, DON'T TOUCH 
ANY BUTTONS".  

I have both normal http and SSL working now. My initial problem 
was, in  the networking module, telling Apache to listen to port 443 
but forgeting to tell it to listen to port 80.

Most importantly is not to use any Webmin configuration buttons 
after that. At least the Slackware install only works with the 
php4.conf and mod_ssl.conf files exclusivly. Clicking the enable ssl 
or any of the module config setting when applied only causes a host 
of errors seen below. A word to the wise, although I think I'm the 
only Slackware user.

Jamie I've attached the php4.conf and mod_ssl.conf files.

Thanks for patience,
Dan


From:           	da...@so...
To:             	Jamie Cameron <jca...@we...>, web...@li...
Subject:        	Re: [webmin-l] virtual interface and SSL
Priority:       	normal
Send reply to:  	web...@li...
	<mailto:web...@li...?subject=unsubscribe>
	<mailto:web...@li...?subject=subscribe>
Date sent:      	Wed, 22 Feb 2006 21:35:21 -0600


I wanted to revisit this now that I have set up a new pristine box. I 
did a clean install of slackware 10.2 manually so as to make sure 
that php4, mod_ssl and Mysql were successfully installed. I let 
slackware install Apache 1.3.33.

The clean http.conf does not contain the load or add modules for 
PhP or mod_ssl but at the end of the file contain INCLUDES:
*********************************************************************
# ==> mod_php configuration settings <==

#
# PACKAGES REQUIRED: openssl-solibs (A series) and/or 
openssl (N series),
# mysql (AP series), gmp (L series), mhash (L series),
# and apache (N series)
#
Include /etc/apache/mod_php.conf

# ==> mod_ssl configuration settings <==
#
# PACKAGES REQUIRED: apache (N series) and openssl (N 
series)
#
Include /etc/apache/mod_ssl.conf
***********************************************************************
this causes php4 and apachessl to appear in the 
apache modules module unchecked, but the server 
still runs. If I check the two mods and try to 
APPLY CHANGES I get:

Syntax error on line 282 of 
/etc/apache/httpd.conf:
Cannot add module via name 'mod_php4.c': not in 
list of loaded modules
***********************************************
Now if I add both php4 and mod_ssl to the loaded 
modules then apply changes things are fine without 
the boxes checked in the apache modules, but there 
is no SSL running. But if I check the php4 and 
apachessl (that keeps appearing) and save, it 
inserts php4 and apachessl into the addmodule in 
http.conf. When I then try to APPLY CHANGES I get:
Syntax error on line 284 of /etc/apache/httpd.conf: Cannot add 
module via name 'mod_apachessl.c': not in list of loaded 
modules
If I modify http.conf load module to apachessl 
then I get:
Syntax error on line 239 of /etc/apache/httpd.conf: Can't locate 
API module structure `apachessl_module' in file 
/usr/libexec/apache/libssl.so: /usr/libexec/apache/libssl.so: 
undefined symbol: apachessl_module

Where does this apachessl come from?

If I remove the apache from the ssl directive the 
server will start fine.

**************************************************
Now when I create a virtual domain through 
virtualmin, with IP address and ssl enabled it 
creates fine. But when I enable ssl for the 
virtual server in the Apache module and restart 
Apache I get: 


Warning: User directive in requires SUEXEC 
wrapper.
Warning: Group directive in requires SUEXEC 
wrapper.
Warning: User directive in requires SUEXEC 
wrapper.
Warning: Group directive in requires SUEXEC 
wrapper.
Syntax error on line 1082 of 
/etc/apache/httpd.conf:
Invalid command 'SSLEnable', perhaps mis-spelled 
or defined by a module not included in the server 
configuration
/usr/sbin/apachectl start: httpd could not be 
started

These are the virtual host directives:

<VirtualHost 69.128.106.188:80>
User "#500"
Group "#500"
ServerName testagain.com
ServerAlias www.testagain.com
DocumentRoot /home/testagain/public_html
ErrorLog /home/testagain/logs/error_log
CustomLog /home/testagain/logs/access_log common
ScriptAlias /cgi-bin/ /home/testagain/cgi-bin/
<Directory /home/testagain/public_html>
Options Indexes IncludesNOEXEC FollowSymLinks
allow from all
</Directory>
</VirtualHost>
<VirtualHost 69.128.106.188:443>
User "#500"
Group "#500"
ServerName testagain.com
ServerAlias www.testagain.com
DocumentRoot /home/testagain/public_html
ErrorLog /home/testagain/logs/error_log
CustomLog /home/testagain/logs/access_log common
ScriptAlias /cgi-bin/ /home/testagain/cgi-bin/
<Directory /home/testagain/public_html>
Options Indexes IncludesNOEXEC FollowSymLinks
allow from all
</Directory>
SSLEngine on
SSLCertificateFile /home/testagain/ssl.cert
SSLCertificateKeyFile /home/testagain/ssl.key
SSLEnable 
</VirtualHost>


Any clue to all this?


Dan





Subject: Re: [webmin-l] virtual interface and SSL
From: Jamie Cameron <jca...@we...>
To: web...@li...
Organization: 
Send reply to: web...@li...
<mailto:webadmin-list-
re...@li...?subject=unsubscribe>
<mailto:webadmin-list-
re...@li...?subject=subscribe>
Date sent: 29 Jan 2006 09:57:53 +1100

[ Double-click this line for list subscription options ] 

On Sun, 2006-01-29 at 01:55, da...@so... wrote:
> What a wonderful work you guys are doing with webmin, it's power 
> continues to grow. Now I don't get into trouble until I experiment 
with 
> undocumented changes ;)
> 
> Problem:
> 
> In my first attempt to set up SSL virtual websites I failed. Jamie's 
> book pointed out that SSL won't work on namebased shared IP. 
So I 
> used Virtualmin to create a virtual IP interface and establish SSL. 
> Apache then created another virtual server with port 443 access 
> giving two virtual servers ( port 80 and 443) both with the new IP. 
> The SSL works great, but port 80 access gives page can't be 
> displayed. Mail seems to work fine. I can't find a way to remove 
the 
> virtual Interface from the virtual server and return it to shared as it 
> was so that the web at least has access for now.
> 
> I then upgraded Virtualmin to 2.610 to no avail. With this 
exception. 
> Now the servers created on Apache show up with a * in the 
address 
> field showing any. I know I shouldn't have experimented on the 
"live" 
> website.
> 
> Questions:
> 
> --Obviously, why doesn't the port 80 access work?
> --How does one remove or change the private IP setting on the 
> server? Virtualmin seems to clamp up once it goes private. And 
> using network interface module to remove it just shuts the entire 
> virtual server down as virtualmin retains the private IP address to 
> the server
> 
> I'm running Webmin 1.250 and Virtualmin 2.610 on a Slackware 
> 10.0 server with Apache 1.3.31

Port 80 certainly should work, so it is probably best to try to solve
that problem .. especially since Virtualmin cannot yet convert a 
server
from private IP back to shared.

What exact error message are you getting when you try the port 80 
URL?
Or is it just displaying the wrong website? Also, what does the
<Virtualhost> section header look like?

- Jamie




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through 
log files
for problems? Stop! Download the new AJAX search engine that 
makes
searching your log files as easy as surfing the web. DOWNLOAD 
SPLUNK!
http://sel.as- 
us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
-
Forwarded by the Webmin mailing list at webadmin- 
li...@li...
To remove yourself from this list, go to
http://lists.sourceforge.net/lists/listinfo/webadmin-list

Re: [webmin-l] virtual interface and SSL

[<da...@so...>]

Hi,
The only expediant thing I could do was delete the server and 
rebuild it without SSL as mail failed and then Apache failed after 
tinkering. I've since created a live test  server to recreate errors 
(waiting for propagation of the new IP as I type.


*****************************************************************************
/usr/sbin/apachectl-mod_ssl


Subject:        	Re: [webmin-l] virtual interface and SSL
From:           	Jamie Cameron <jca...@we...>
To:             	web...@li...
Organization:   	
Send reply to:  	web...@li...
	<mailto:web...@li...?subject=unsubscribe>
	<mailto:web...@li...?subject=subscribe>
Date sent:      	29 Jan 2006 09:57:53 +1100

[ Double-click this line for list subscription options ] 

On Sun, 2006-01-29 at 01:55, da...@so... wrote:
> What a wonderful work you guys are doing with webmin, it's power 
> continues to grow. Now I don't get into trouble until I experiment with 
> undocumented changes ;)
> 
> Problem:
> 
> In my first attempt to set up SSL virtual websites I failed. Jamie's 
> book pointed out that SSL won't work on namebased shared IP. So I 
> used Virtualmin to create a virtual IP interface and establish SSL. 
> Apache then created another virtual server with port 443 access 
> giving two virtual servers ( port 80 and 443) both with the new IP. 
> The SSL works great, but port 80 access gives page can't be 
> displayed. Mail seems to work fine. I can't find a way to remove the 
> virtual Interface from the virtual server and return it to shared as it 
> was so that the web at least has access for now.
> 
> I then upgraded Virtualmin to 2.610 to no avail. With this exception. 
> Now the servers created on Apache show up with a * in the address 
> field showing any. I know I shouldn't have experimented on the "live" 
> website.
> 
> Questions:
> 
> --Obviously, why doesn't the port 80 access work?
> --How does one remove or change the private IP setting on the 
> server? Virtualmin seems to clamp up once it goes private. And 
> using network interface module to remove it just shuts the entire 
> virtual server down as virtualmin retains the private IP address to 
> the server
> 
> I'm running Webmin 1.250 and Virtualmin 2.610 on a Slackware 
> 10.0 server with Apache 1.3.31

Port 80 certainly should work, so it is probably best to try to solve
that problem .. especially since Virtualmin cannot yet convert a 
server
from private IP back to shared.

What exact error message are you getting when you try the port 80 
URL?
Or is it just displaying the wrong website? Also, what does the
<Virtualhost> section header look like?

 - Jamie




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through 
log files
for problems?  Stop!  Download the new AJAX search engine that 
makes
searching your log files as easy as surfing the  web.  DOWNLOAD 
SPLUNK!
http://sel.as-
us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
-
Forwarded by the Webmin mailing list at webadmin-
li...@li...
To remove yourself from this list, go to
http://lists.sourceforge.net/lists/listinfo/webadmin-list

Re: [webmin-l] virtual interface and SSL

[<da...@so...>]

I wanted to revisit this now that I have set up a new pristine box. I 
did a clean install of slackware 10.2 manually so as to make sure 
that php4, mod_ssl and Mysql were successfully installed. I let 
slackware install Apache 1.3.33.

The clean http.conf does not contain the load or add modules for 
PhP or mod_ssl but at the end of the file contain INCLUDES:
*********************************************************************
# ==> mod_php configuration settings <==

#
# PACKAGES REQUIRED:  openssl-solibs (A series) and/or 
openssl (N series),
#                     mysql (AP series), gmp (L series), mhash (L series),
#                     and apache (N series)
#
Include /etc/apache/mod_php.conf

# ==> mod_ssl configuration settings <==
#
# PACKAGES REQUIRED:  apache (N series) and openssl (N 
series)
#
Include /etc/apache/mod_ssl.conf
***********************************************************************
this causes php4 and apachessl to appear in the 
apache modules module unchecked, but the server 
still runs. If I check the two mods and try to 
APPLY CHANGES I get:

 Syntax error on line 282 of 
/etc/apache/httpd.conf:
Cannot add module via name 'mod_php4.c': not in 
list of loaded modules
***********************************************
Now if I add both php4 and mod_ssl to the loaded 
modules then apply changes things are fine without 
the boxes checked in the apache modules, but there 
is no SSL running. But if I check the php4 and 
apachessl (that keeps appearing) and save, it 
inserts php4 and apachessl into the addmodule in 
http.conf. When I then try to APPLY CHANGES I get:
Syntax error on line 284 of /etc/apache/httpd.conf: Cannot add 
module via name 'mod_apachessl.c': not in list of loaded 
modules
If I modify http.conf load module to apachessl 
then I get:
Syntax error on line 239 of /etc/apache/httpd.conf: Can't locate 
API module structure `apachessl_module' in file 
/usr/libexec/apache/libssl.so: /usr/libexec/apache/libssl.so: 
undefined symbol: apachessl_module

Where does this apachessl come from?

If I remove the apache from the ssl directive the 
server will start fine.

**************************************************
Now when I create a virtual domain through 
virtualmin, with IP address and ssl enabled it 
creates fine. But when I enable ssl for the 
virtual server in the Apache module and restart 
Apache I get: 


Warning: User directive in  requires SUEXEC 
wrapper.
Warning: Group directive in  requires SUEXEC 
wrapper.
Warning: User directive in  requires SUEXEC 
wrapper.
Warning: Group directive in  requires SUEXEC 
wrapper.
Syntax error on line 1082 of 
/etc/apache/httpd.conf:
Invalid command 'SSLEnable', perhaps mis-spelled 
or defined by a module not included in the server 
configuration
/usr/sbin/apachectl start: httpd could not be 
started

These are the virtual host directives:

<VirtualHost 69.128.106.188:80>
User "#500"
Group "#500"
ServerName testagain.com
ServerAlias www.testagain.com
DocumentRoot /home/testagain/public_html
ErrorLog /home/testagain/logs/error_log
CustomLog /home/testagain/logs/access_log common
ScriptAlias /cgi-bin/ /home/testagain/cgi-bin/
<Directory /home/testagain/public_html>
Options Indexes IncludesNOEXEC FollowSymLinks
allow from all
</Directory>
</VirtualHost>
<VirtualHost 69.128.106.188:443>
User "#500"
Group "#500"
ServerName testagain.com
ServerAlias www.testagain.com
DocumentRoot /home/testagain/public_html
ErrorLog /home/testagain/logs/error_log
CustomLog /home/testagain/logs/access_log common
ScriptAlias /cgi-bin/ /home/testagain/cgi-bin/
<Directory /home/testagain/public_html>
Options Indexes IncludesNOEXEC FollowSymLinks
allow from all
</Directory>
SSLEngine on
SSLCertificateFile /home/testagain/ssl.cert
SSLCertificateKeyFile /home/testagain/ssl.key
SSLEnable 
</VirtualHost>


Any clue to all this?


Dan





Subject:        	Re: [webmin-l] virtual interface and SSL
From:           	Jamie Cameron <jca...@we...>
To:             	web...@li...
Organization:   	
Send reply to:  	web...@li...
	<mailto:web...@li...?subject=unsubscribe>
	<mailto:web...@li...?subject=subscribe>
Date sent:      	29 Jan 2006 09:57:53 +1100

[ Double-click this line for list subscription options ] 

On Sun, 2006-01-29 at 01:55, da...@so... wrote:
> What a wonderful work you guys are doing with webmin, it's power 
> continues to grow. Now I don't get into trouble until I experiment with 
> undocumented changes ;)
> 
> Problem:
> 
> In my first attempt to set up SSL virtual websites I failed. Jamie's 
> book pointed out that SSL won't work on namebased shared IP. So I 
> used Virtualmin to create a virtual IP interface and establish SSL. 
> Apache then created another virtual server with port 443 access 
> giving two virtual servers ( port 80 and 443) both with the new IP. 
> The SSL works great, but port 80 access gives page can't be 
> displayed. Mail seems to work fine. I can't find a way to remove the 
> virtual Interface from the virtual server and return it to shared as it 
> was so that the web at least has access for now.
> 
> I then upgraded Virtualmin to 2.610 to no avail. With this exception. 
> Now the servers created on Apache show up with a * in the address 
> field showing any. I know I shouldn't have experimented on the "live" 
> website.
> 
> Questions:
> 
> --Obviously, why doesn't the port 80 access work?
> --How does one remove or change the private IP setting on the 
> server? Virtualmin seems to clamp up once it goes private. And 
> using network interface module to remove it just shuts the entire 
> virtual server down as virtualmin retains the private IP address to 
> the server
> 
> I'm running Webmin 1.250 and Virtualmin 2.610 on a Slackware 
> 10.0 server with Apache 1.3.31

Port 80 certainly should work, so it is probably best to try to solve
that problem .. especially since Virtualmin cannot yet convert a 
server
from private IP back to shared.

What exact error message are you getting when you try the port 80 
URL?
Or is it just displaying the wrong website? Also, what does the
<Virtualhost> section header look like?

 - Jamie




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through 
log files
for problems?  Stop!  Download the new AJAX search engine that 
makes
searching your log files as easy as surfing the  web.  DOWNLOAD 
SPLUNK!
http://sel.as-
us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
-
Forwarded by the Webmin mailing list at webadmin-
li...@li...
To remove yourself from this list, go to
http://lists.sourceforge.net/lists/listinfo/webadmin-list