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

Avon_Fox
Aspirant
Feb 17, 2012
Multiple websites not working with removal of www from the URL.

I've got my RNPD200U set up with Virtual.conf and my-virtual.conf as shown below and it works fine for the 'www.the-liberator.net' URL but the 'the-liberator.net' URL fails. I've removed the DNS entry to the latter as it was confusing Google's indexing but I'd like to get it to work.

I had DNS A record set up for both www.the-liberator.net and the-liberator.net which worked fine on my old Windows web server but with the .conf files set as below it fails to work with for the www-less URL.

Any ideas greatly welcome. I can set up the A record again if anyone wants to test anything.

Cheers folks!

Virtual.conf

NameVirtualHost *:80

<VirtualHost *:80>
SSLEngine off
RewriteEngine on

RewriteRule ^/admin/(.*)$ https://%{SERVER_NAME}/admin/$1 [R,L]
</VirtualHost>

my-virtual.conf

<VirtualHost *:80>
ServerName www.the-liberator.net
DocumentRoot /c/web
<Directory /c/web>
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 the-liberator.net
DocumentRoot /c/web
<Directory /c/web>
Options Indexes
Order allow,deny
Allow from all
</Directory>
<Location /index.html>
SetHandler none
Order Allow,Deny
Allow from all
</Location>
SSLEngine off
</VirtualHost>
WhoCares_
Mentor
Feb 17, 2012
Why don't you just remove the second <VirtualHost>...</VirtualHost> section and add a 'ServerAlias the-liberator.net' statement to the first?

-Stefan
Avon_Fox
Aspirant
Feb 18, 2012
Why don't you just remove the second <VirtualHost>...</VirtualHost> section and add a 'ServerAlias the-liberator.net' statement to the first?

Because I have much to learn. :wink: Thanks for the advice. My my-virtual.conf now looks like this (below).

I've re-added the A record to the-liberator.net to my DNS hosting service (I needed to do that right?) and am now waiting for DNS to update so I can test it.
I'll report back in a day and see how we went!

Thanks very much for your suggestion!

<VirtualHost *:80>
ServerName http://www.the-liberator.net
ServerAlias the-liberator.net
DocumentRoot /c/web
<Directory /c/web>
Options Indexes
Order allow,deny
Allow from all
</Directory>
<Location /index.html>
SetHandler none
Order Allow,Deny
Allow from all
</Location>
SSLEngine off
</VirtualHost>
Avon_Fox
Aspirant
Feb 19, 2012
THANK YOU very much for your help. Now that DNS has updated and with the ServerAlias entry in my-virtual.conf it's resolving perfectly!

Very, very happy!
WhoCares_
Mentor
Feb 19, 2012
Glad I could be of help.

-Stefan
Avon_Fox
Aspirant
Feb 24, 2012
I do still have the problem above the last where indexes are not being created with mod_autoindex for directories in the /c/web/ directory.

They are generated fine for any shares that have HTTP enabled via Frontview but not through the method described in this topic.

Does anyone know which files and settings govern which folders mod_autoindex is applied to?

ericclaeren

Aspirant

Feb 24, 2012

Hi,

Hopefully someone can help me, i'm stuck and have quite some regrets buying a ReadyNas Pro.

Got the Virtualhost working through this topic, thanks!

But ran into this problem. Images aren't shown on my site(s). I have a virtual site, call it example. It's in this dir /c/www/example
In my document root is a directory called /images, when I check the error.log file it says:

[Fri Feb 24 17:13:59 2012] [error] [client 192.168.1.4] File does not exist: /frontview/ui/resource/images/menu, referer: http://example.site/

It seems it rewrites the image folder of my current example site to /frontview/ui/resource/images

When looking at http.conf


Alias /images/ /frontview/ui/resource/images/
<Directory /images>
    Options MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
</Directory>
Alias /theme/ /frontview/ui/resource/theme/
<Directory /theme>
    Options MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
</Directory>
Alias /js/ /frontview/ui/resource/js/
<Directory /js>
    Options MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
</Directory>

Alias /language/ /frontview/ui/resource/language/
<Directory /language>
    Options MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
</Directory>
Alias /addons/ /etc/frontview/addons/ui/
<Directory /addons>
    Options MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
</Directory>
Alias /html/ /frontview/ui/resource/html/
<Directory /html>
    Options MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
</Directory>

Alias /admin /frontview/ui/resource/html
<Location /admin>
    DirectoryIndex index.html
    Options ExecCGI
    Include /etc/frontview/apache/Auth.conf
    AuthName "Control Panel"
    require user admin
</Location>

There are a number of default aliasses set to a location, how can I override these? Admin and Images are quite often used directories.

My virtual host file


<VirtualHost *:80>
  ServerName www.example.site
  ServerAlias example.site

  DocumentRoot /www/example

  <Directory /www/example>
    Options +Indexes +MultiViews +FollowSymLinks
    AllowOverride All
    Order allow,deny
    Allow from all
  </Directory>

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

  SSLEngine off
</VirtualHost>

Really hope somebody has an Idea how this can be fixed.
Thanks!!

WhoCares_
Mentor
Feb 24, 2012
Have a look at my repository at Gitorious: http://gitorious.org/readynas
In the apache-config section you should find some hints.

-Stefan
Avon_Fox
Aspirant
Feb 25, 2012
Thanks again Stefan. I'll have a look. I see now you've posted this above too. No idea how I missed it the first time!
I think it's probably beyond my level of experience to work it out but if I do I'll post back the results.

ericclaeren

Aspirant

Feb 26, 2012

Hi Stefan,

Thanks, I tried your apache Frontview version, but unfortunately they did not work for me, could not get apache running, Tried to move some parts around, but I'm not comfortable with that and didn't got it working.

Really thought when buying this NAS running a web server would be a piece of cake, just like a regular linux apache2 setup. So disappointed with this machine.
I can't understand why the developers of the ReadyNas did not separate the frontview interface from the apache setup like a regular site. Would have made things so much easier.

Thanks

These were the errors i got:


[Sun Feb 26 23:00:37 2012] [warn] module php5_module is already loaded, skipping
nas-eric:/etc/frontview/apache/addons# tail /var/log/frontview/error.log
[Sun Feb 26 22:48:01 2012] [error] Can't locate Frontview.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/                               share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl . /frontview/ui/resource/html) at (eval 2) line 3.\n
[Sun Feb 26 22:48:01 2012] [error] Can't load Perl module Frontview for server localhost:80, exiting...
[Sun Feb 26 22:49:09 2012] [error] Can't locate Frontview.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/                               share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl . /frontview/ui/resource/html) at (eval 2) line 3.\n
[Sun Feb 26 22:49:09 2012] [error] Can't load Perl module Frontview for server localhost:443, exiting...
[Sun Feb 26 22:53:33 2012] [error] Can't locate Frontview.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/                               share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl . /frontview/ui/resource/html) at (eval 2) line 3.\n
[Sun Feb 26 22:53:33 2012] [error] Can't load Perl module Frontview for server localhost:443, exiting...
[Sun Feb 26 22:54:21 2012] [error] Can't locate Frontview.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/                               share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl . /frontview/ui/resource/html) at (eval 2) line 3.\n
[Sun Feb 26 22:54:21 2012] [error] Can't load Perl module Frontview for server localhost:443, exiting...
[Sun Feb 26 23:00:37 2012] [error] Can't locate Frontview.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/                               share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl . /frontview/ui/resource/html) at (eval 2) line 3.\n
[Sun Feb 26 23:00:37 2012] [error] Can't load Perl module Frontview for server localhost:443, exiting...

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