G'day Guys,For some time I've wanted to host multiple websites from a single ReadyNAS unit...I haven't had the time to investigate it.1. Backup all the .conf files in /etc/frontview/apache2. Backup all the .conf files in /etc/frontview/apache - so you can restore the originals if you screw something up !!!3. Edit /etc/frontview/apache/Virtual.confOriginal file<VirtualHost _default_:80> SSLEngine off RewriteEngine on RewriteRule ^/admin/(.*)$ https://%{SERVER_NAME}/admin/$1 [R,L]</VirtualHost>Modified fileNameVirtualHost *:80<VirtualHost *:80> SSLEngine off RewriteEngine on RewriteRule ^/admin/(.*)$ https://%{SERVER_NAME}/admin/$1 [R,L]</VirtualHost>4. Create a new my-virtual.conf file in /etc/frontview/apache/addons, this way it will be auto loaded without modifying any other files. The example below has definitions for two websites....add/remove as required.my-virtual.conf<VirtualHost *:80> ServerName www.example.com DocumentRoot /path/to/example.com <Directory /path/to/example.com> Options Indexes Order allow,deny Allow from all </Directory> <Location /index.html> SetHandler none Order Allow,Deny Allow from all </Location> SSLEngine off</VirtualHost><VirtualHost *:80> ServerName www.domain.net DocumentRoot /path/to/domain.net <Directory /path/to/domain.net> Options Indexes Order allow,deny Allow from all </Directory> <Location /index.html> SetHandler none Order Allow,Deny Allow from all </Location> SSLEngine off</VirtualHost>5. shutdown apache, killall apache-ssl6. restart apache, apache-ssl -f /etc/frontview/apache/httpd.conf7. All done :D CAVEATS1. Toggling the state of HTTP within Frontview rewrites Virtual.conf so the above changes will be lost.ReadyNAS Team1. It would be nice if the above changes could be made to the format of /etc/frontview/apache/Virtual.conf, so that changes aren't overwritten2. I currently have to add the Location element to undo a global definition within httpd.conf. It would be awesome if this was removed from httpd.conf and added to Virtual.conf as...NameVirtualHost *:80<VirtualHost *:80> <Location /index.html> SetHandler server-status Order Deny,Allow Deny from all </Location> SSLEngine off RewriteEngine on RewriteRule ^/admin/(.*)$ https://%{SERVER_NAME}/admin/$1 [R,L]</VirtualHost>Cheers,David

why not using /etc/frontview/apache/addons/ for this ?

super-poussin wrote:why not using /etc/frontview/apache/addons/ for this ?Step 4 uses that location, however, the way /etc/frontview/apache/Virtual.conf has been defined....it really doesn't allow expansion, hence the reason for modifying it. You can't have mixed declarations of <VirtualHost _default_:80> and <VirtualHost *:80> as the first one declared will always be used.

Nice how-to... thanks for sharing.Does this still require these steps?http://www.readynas.com/?p=135Currently, I've got my blog-thingy hosted on the ReadyNAS Pro. In Frontview, under the HTTP protocol I am redirecting HTTP traffic to the read-only HTTP share "webserver". How does your how-to fit in with this?Notice that when you try to go to my site http://home.bott.ca/ in automatically redirects to the webserver share (as I expect it would - http://home.bott.ca/webserver/).Do all websites have to be placed within this "webserver" share?I guess I'm just a bit confused as to how this works. If you've got any sites hosted on your NAS where you can provide an example, I'd love to see it in action.Regards,Dave

I don't use that option, I currently have it set to 'None Selected'. Using that options adds an additional rewrite rule to /etc/frontview/apache/Virtual.conf, something like this...RewriteRule ^/$ /webserver [R,L]Instead, I have a single share called 'Sites' with a folder for each site that I have configured, then the my-virtual.conf sets the DocumentRoot to the specific Site folder. But I have only done this to make my life easy for updating content. Each site could exist on totally different shares, there is no restriction on that.I'm not hosting anything elaborate, just some firefox extensions and other stuff that I hack around with, here's two sites that are currently hosted off my NAS...http://www.smugglr.nethttp://smugbrowser.introversion.com.au/beta

dbott67 wrote:Nice how-to... thanks for sharing.Does this still require these steps?http://www.readynas.com/?p=135No, actually the approach from this Howto is more flexible but requires more work and a lot more knowledge about how things "really work".dbott67 wrote:Currently, I've got my blog-thingy hosted on the ReadyNAS Pro. In Frontview, under the HTTP protocol I am redirecting HTTP traffic to the read-only HTTP share "webserver". How does your how-to fit in with this?Two totally different beasts. The way you do it will create a config similar to this:<VirtualHost _default_:80> SSLEngine off RewriteEngine on RewriteRule ^/$ /website [R,L] RewriteRule ^/admin/(.*)$ https://%{SERVER_NAME}/admin/$1 [R,L]</VirtualHost>The important part is line 4 where all requests are redirected to the Share "website". That's what you already noticed here:dbott67 wrote:Notice that when you try to go to my site http://home.bott.ca/ in automatically redirects to the webserver share (as I expect it would - http://home.bott.ca/webserver/).While this works, it will just allow you to host one website on your NAS.Comes in the Howto. The important part here is that you can have not only one but several <VirtualHost ...> entries.This leads straight to your next question:dbott67 wrote:Do all websites have to be placed within this "webserver" share?No. Let's have a look at the VirtualHost definition:<VirtualHost *:80> ServerName www.example.com DocumentRoot /path/to/example.com <Directory /path/to/example.com> Options Indexes Order allow,deny Allow from all </Directory> <Location /index.html> SetHandler none Order Allow,Deny Allow from all </Location> SSLEngine off</VirtualHost>Notice line 3. The DocumentRoot ... tells Apache where to look for the files it should serve to the user. In this case this would be /path/to/example.comAlso important is line 2. The ServerName ... tells Apache what site this configuration is meant for.A simple, yet very abbreviated example:<VirtualHost *:80>ServerName server1.dyndns.orgDocumentRoot /website1(...)</VirtualHost><VirtualHost *:80>ServerName anotherserver.dyndns.orgDocumentRoot /website2(...)</VirtualHost>Now what happens when a request comes in is this: Apache will look in the headers for the host name the user wanted to address. Say the user requested "anotherserver.dyndns,org". Apache finds the defintion for that server, looks into the directory /website2 and will serve the file index.html if it's to be found there. (That's an overly simplistic explanation but you should get the drift). /website2 doesn't have to be a share, it just has to exist.Likewise, since all Apache cares about is the host name, not the IP address, "server1.dyndns.org" and "anotherserver.dyndns.org" may of course point to the same (your public) IP address.I really hope this was somewhat understandable since I tried to cramp many things in a "not too long to digest" post ;)-Stefan

HOW TO: Hosting multiple websites

129 Replies

Replies have been turned off for this discussion

leoj3n

Aspirant

Jul 15, 2012

Stefan,

I tried re-applying your patch. Here is how:

alfa-nas:/etc/frontview# ls apache.bak/ #<--- Config before apply WhoCares?'s patch
04d1e7c3.0  addons  apache.pem	Auth.conf  httpd.conf  Ports.conf  Shares.conf	Shares.conf.1  Shares.conf.2  ssleay.cnf  Virtual.conf
alfa-nas:/etc/frontview# ls apache.add/ #<--- Pulled from Gitorious                
Auth.conf  AuthVhost.conf  DefAlias.conf  httpd.conf  PerlSettings.conf  Ports.conf  ssleay.cnf  Virtual.conf
alfa-nas:/etc/frontview# rm -rf apache                             
alfa-nas:/etc/frontview# cp -rf apache.bak/ apache
alfa-nas:/etc/frontview# cp -rf apache.add/* apache
alfa-nas:/etc/frontview# ls apache.upd/sites/ #<--- My custom *.vhost files
2011cc.otzo.com.vhost  leoj3n.no-ip.org.vhost  leoj3n.otzo.com.vhost  mom.otzo.com.vhost
alfa-nas:/etc/frontview# cp apache.upd/sites/*.vhost apache/addons/
alfa-nas:/etc/frontview# ls apache                                         
04d1e7c3.0  apache.pem	AuthVhost.conf	httpd.conf	   Ports.conf	Shares.conf.1  ssleay.cnf
addons	    Auth.conf	DefAlias.conf	PerlSettings.conf  Shares.conf	Shares.conf.2  Virtual.conf
alfa-nas:/etc/frontview# ls apache/addons/
2011cc.otzo.com.vhost  leoj3n.no-ip.org.vhost  mom.otzo.com.vhost  PHPMYADMIN.conf	 RSNAPSHOT.conf
DNSOMATIC.conf	       leoj3n.otzo.com.vhost   phpadmweb.conf	   PLEXMEDIASERVER.conf


alfa-nas:/etc/frontview# apache-ssl -f /etc/frontview/apache/httpd.conf -k restart -V
Server version: Apache/2.2.6 (Debian)
Server built:   Feb 28 2008 22:43:28
Server's Module Magic Number: 20051115:5
Server loaded:  APR 1.2.7, APR-Util 1.2.7
Compiled using: APR 1.2.7, APR-Util 1.2.7
Architecture:   32-bit
Server MPM:     Prefork
  threaded:     no
    forked:     yes (variable process count)
Server compiled with....
 -D APACHE_MPM_DIR="server/mpm/prefork"
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_SYSVSEM_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=128
 -D HTTPD_ROOT=""
 -D SUEXEC_BIN="/bin/suexec"
 -D DEFAULT_PIDLOG="/var/run/apache2.pid"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_LOCKFILE="/var/run/apache2/accept.lock"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="/etc/apache2/mime.types"
 -D SERVER_CONFIG_FILE="/etc/apache2/apache2.conf"

Just trying to eliminate any possible causes of the problems I am still facing. Any ideas? :(

leoj3n

Aspirant

Jul 15, 2012

leoj3n wrote:
Changing from /sites/ to /addons/ was fruitless. However I tried going to http://2011cc.otzo.com/index.php which gives the output:
Your server is running PHP version 5.2.0-8+etch16 but WordPress 3.4.1 requires at least 5.2.4.

However if you don't go directly to the index.php file you still get the permissions thing: http://2011cc.otzo.com/

An update: I finally thought to remove the .htaccess included with (correction: generated by, because I copied the WordPress files from my Desktop which was running a webserver and active WordPress install) WordPress and now the permission error goes away when you visit http://2011cc.otzo.com/

Going to http://2011cc.otzo.com/ does a directory-listing however, and doesn't automatically query index.php - that is what I will work on next.
Update: I had removed the following from the custom .vhost file during testing:

  <Location />    
    DirectoryIndex redirect.html index.html index.htm index.php
  </Location>

Adding it back causes index.php to be downloaded when visiting http://2011cc.otzo.com/ or http://2011cc.otzo.com/index.php ...

WhoCares_
Mentor
Jul 15, 2012
My best guess right now is that by jsut copying over the existing files some fragments still interfere with the general operation of your Apache config. Try removing the apache config dir completey (of course only after you've made yet another backup ;)) and copy over the x86 config from the gitorious repo. Then copy back the add-on subdir. Also, if I'm not completely mistaken there should be an installer script in the repo, no?

-Stefan

leoj3n

Aspirant

Jul 15, 2012

Unfortunately I totally missed the install.sh script when I started this whole charade. I just copied the x86 dir using cp, and that's what I've been doing up until this point. Sorry for my ignorance, I've never run a .sh file until today.

To attempt to start from scratch I did the following, please look this over (apache.bak is the backup of the original /apache/ folder, made before doing any modifications):

alfa-nas:/etc/frontview# rm -rf apache                                                      
alfa-nas:/etc/frontview# cp -rf apache.bak/ apache                                          
alfa-nas:/etc/frontview# apache-ssl -f /etc/frontview/apache/httpd.conf -k restart          
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 10.0.1.2 for ServerName
alfa-nas:/etc/frontview# cd /c/home/admin/System\ Stuff/NAS/apache-configs/
alfa-nas:/c/home/admin/System Stuff/NAS/apache-configs# sudo bash install.sh 
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 10.0.1.2 for ServerName
Syntax OK
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 10.0.1.2 for ServerName
alfa-nas:/c/home/admin/System Stuff/NAS/apache-configs# cd -
/etc/frontview
alfa-nas:/etc/frontview# cp apache.upd2/addons/2011cc.otzo.com.vhost apache/addons/         
alfa-nas:/etc/frontview# apache-ssl -f /etc/frontview/apache/httpd.conf -k restart 
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 10.0.1.2 for ServerName
alfa-nas:/etc/frontview# cat apache/addons/2011cc.otzo.com.vhost 
<VirtualHost *:80>
  ServerName 2011cc.otzo.com
  ServerAlias 2011cc.otzo.com
  DocumentRoot /c/public_html/2011cc 

  #LoadModule php5_module /usr/lib/apache2/modules/libphp5.so
  #AddHandler php5-script .php
  #AddType text/html .php
  #AddType application/x-httpd-php .php                                                  
  #AddType application/x-httpd-php-source .phps                                          

  <Directory /c/public_html/2011cc>
    Options +FollowSymLinks +ExecCGI
    AllowOverride All
    Order Allow,Deny
    Allow from all
  </Directory>

  <Location />    
    #Options ExecCGI
    DirectoryIndex redirect.html index.html index.htm index.php
  </Location>

  <Location /index.html>
    SetHandler none
    Order Allow,Deny
    Allow from all
  </Location>

  SSLEngine off
  RewriteEngine On
  RewriteOptions Inherit
  Options +FollowSymLinks
</VirtualHost>

alfa-nas:/etc/frontview#

PHP files are still being downloaded instead of output to the browser. I even tried restarting the NAS (just for fun?) but the problem persists.

Thanks for all your attention Stefan. Does your config on your server serve up PHP files correctly? If so I think we can narrow this down to php_mod being installed incorrectly. At that point I will probably try using your FrontView PHP add-on.

WhoCares_
Mentor
Jul 15, 2012
Actually my config does nothing to allow/prevent PHP scripts from being executed / served to the user. This should be handled by the libapache2-mod-php5 module. Unfortunately this will add it's config to a file that isn't read by the ReadyNAS' Apache web server. What you can try to do is to create the file '/etc/frontview/apache/addons/00_phpload.conf' with this contents:
<IfModule mod_php5.c>
LoadModule php5_module /usr/lib/apache2/modules/libphp5.so
AddHandler php5-script .php
AddType text/html .php
AddType application/x-httpd-php .php
AddType application/x-httpd-php-source .phps
</IfModule>

Restart Apache and see whether this changed anything.

-Stefan
leoj3n
Aspirant
Jul 15, 2012
No, no changes. In the custom vhost I tried
<Location />
DirectoryIndex redirect.html index.html index.htm index.php
</Location>
and
<Location />
Options ExecCGI
DirectoryIndex redirect.html index.html index.htm index.php
</Location>

but that had no effect either. When I visit http://2011cc.otzo.com/ it still just downloads the damned PHP file. :evil:

The output of apache-ssl -f /etc/frontview/apache/httpd.conf -M contains no references to php.

leoj3n

Aspirant

Jul 15, 2012

Stefan (WhoCares?) helped me privately and we got it sorted. I posted the critical factor here: viewtopic.php?f=35&t=64537

Here's my final config, it should be useful to anyone else trying to set up virtual hosts + PHP (& I've included an example that fixes directory images): http://leoj3n.otzo.com/example-apache-a ... fig.tar.gz

Important files:


/etc/frontview/apache/addons/sub.domain.com.vhost         #example virtual host
/etc/frontview/apache/addons/dirlist.domain.com.vhost     #example virtual host that supports directory images
/etc/frontview/apache/addons/domain.com.vhost             #example virtual host that utilizes ServerAlias
/etc/frontview/apache/addons/00_php5module.conf           #php5 config file; without this .php files download instead of output to the browser

Here are the steps the I believe resulted in my eventual success:

First, backup your current configuration

cp -rf /etc/frontview/apache/ /etc/frontview/apache.bak/

Change settings in FrontView -> Standard File Protocols -> HTTP

Redirect default web access to this share: None selected
Login authentication on this share: Disable

Clone WhoCares?'s apache-configs repo on Gitorious

Link: https://gitorious.org/readynas/apache-configs

Git clone command:

git clone git://gitorious.org/readynas/apache-configs.git apache-configs

Run the apache-configs install file

cd ./apache-configs/; sudo bash install.sh

Create a .vhost file in /etc/frontview/apache/addons/

cd /etc/frontview/apache/addons/; touch YOUR.DOMAIN.com.vhost

The contents of YOUR.DOMAIN.com.vhost should be something like:

<VirtualHost *:80>
  ServerName YOUR.DOMAIN.com
  DocumentRoot /YOUR_HTML_SHARE/a_sub_dir
                                  
  <Directory /YOUR_HTML_SHARE/a_sub_dir>
    Options +FollowSymLinks +ExecCGI
    AllowOverride All               
    Order Allow,Deny 
    Allow from all  
  </Directory>    
              
  DirectoryIndex redirect.html index.html index.htm index.php
                                                             
  <Location /index.html>
    SetHandler none     
    Order Allow,Deny
    Allow from all  
  </Location>     
             
  SSLEngine off
  RewriteEngine On
  RewriteOptions Inherit
  Options +FollowSymLinks
</VirtualHost>

Restart Apache

apache-ssl -f /etc/frontview/apache/httpd.conf -k restart

mattkingston
Aspirant
Sep 29, 2012
Hi all,

Very sorry im several years late with this one.

Im a little new to this virtual hosting bu i wish to host more than one website on my Readynas Duo

I can across a very usefull guide here on how to setup for multiple hosts with the virtual.conf file however, im unsure how to get to this file in order to modify it.
I cant find it via windows explorer so i assume i must use ssl??? (which im also new too)

Any tips on the best way to modify the conf file would be great.

thanks in advance!
Assassins
Aspirant
Feb 09, 2013
Hmmmm this guide work not on the Duo v1 2110
I get a blank site :(

I have try this guide many time now, and same result...

Forum Discussion

HOW TO: Hosting multiple websites

129 Replies

Related Content

ReadyNAS 102 host website including JavaScript

Websites Blocked

RBR850 blocking certain websites

RBR760 MULTIPLE ISSUES

GS748Tv5 VLAN hosts can't communicate

NETGEAR Academy

ProSupport for Business