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

devbobo

Aspirant

Nov 29, 2009

HOW TO: Hosting multiple websites

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/apache
2. 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.conf

Original file


<VirtualHost _default_:80>
  SSLEngine off
  RewriteEngine on

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

Modified file


NameVirtualHost *: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-ssl
6. restart apache, apache-ssl -f /etc/frontview/apache/httpd.conf
7. All done :D

CAVEATS
1. Toggling the state of HTTP within Frontview rewrites Virtual.conf so the above changes will be lost.

ReadyNAS Team
1. 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 overwritten
2. 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

ReadyNAS Developers Network

129 Replies

Replies have been turned off for this discussion

montrose_it
Aspirant
Apr 12, 2011
ok done - i had a problem with using www.mysubsite.xxxxxx.com as my domain name hence the reason of the post above.
i am now using mysubsite.xxxxx.com otherwise it just defaults to /shares - must be a problem with my domain provider :(

anyway all working so i'm not bothered :)

what i am bothered with is my downloads web page - has any one got experiance with this?

Progressed

Aspirant

Jul 10, 2011

Hoping someone can help me... Im trying to solve a .htaccess problem what gave me the following error from apache errorlog:

Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that RewriteRule directive is forbidden: /c/websites/

when searching for the solution i came accros this topic and i want to host more websites :)

So i converted my website (set in frontview) to a virtual host... But I would like to get the authentication back to what it was... and that is checking the usergroups i authenticated on the folder!

Heres my VH:

<VirtualHost *:80>
  Servername projects.prog.nl
  DocumentRoot /c/websites
    <Directory /c/websites>
      Options Indexes
      Order allow,deny
      Allow from all
      AllowOverride all
      DirectoryIndex index.php index.html
    </Directory>
    <Location /c/websites>
      AuthName "Restricted"
      AuthType Basic
      Require valid-user
    </Location>
  SSLEngine off
</VirtualHost>

BigHoskey
Aspirant
Aug 24, 2011
I have read two books and did a lot of line commands on Linux Mint to get a better understanding on how everything works. Well I was ready to set up the ReadyNas Nv+ with the new my-virtual.conf file in /etc/frontview/apache/addons. But this is my problem how do I login to the SSH addon. After I rebooted the Readynas after installing everything, whats next?
Bartezz
Aspirant
Oct 01, 2011
Am very new to all this and don't know a thing about command lines since the extinction of commodore 64 :)
Is there an add-on thru which I could achieve a multi site setup via a gui? Or is one in the making?

Cheers
cmonard
Aspirant
Nov 17, 2011
Hello All!

I've followed you indication, try many version but, the readynas duo still redirect my domain name to /shares/ directory.

Don't understand why it does this.

Can someone help me?

Thanks a lot!
cmonard
Aspirant
Nov 24, 2011
Hello I've found the answer,

When you create your new share for a website, don't make it accessible to the web via "share list" > "http/s" > "access" => "read" // that is the wrong way. Juste leave it to "no access".

Then the conf in your Virtual.conf should take effect. :)

Nice
Avon_Fox
Aspirant
Jan 08, 2012
devbobo, this worked a treat!

Thank you so much. After moving from an old Windows server and then having to have /sharename/ in the URL killed all my built up indexing with Google and there was nothing they could do about it.

So very happy! :D
Avon_Fox
Aspirant
Jan 10, 2012
I've started a new topic for this but I probably should have posted it here in hindsight. If either gets the problem solved I'll link one to the other.

Hi there, this one has me boggled so I'm hoping you can help.
I'm running 4.1.7

I've modified my /etc/frontview/apache/Virtual.conf and added a my-virtual.conf to /etc/frontview/apache/addons as detailed earlier in this topic and it all went well.

My problem is that some folders in the /web/ directory (where I keep my web files) have indexes and some are just folders of files that I need to access without an index.
My my-virtual.conf file has "Options Indexes" listed but when I web surf to those index free folders I get "Forbidden You don't have permission to access /apps/ on this server."

Shouldn't mod_autoindex generate a directly listing or is it not supported on the ReadyNAS?

Cheers for any help/ideas you fine folks can offer.

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 http://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>
WhoCares_
Mentor
Jan 10, 2012
Try using "+Indexes +MultiViews" instead of just "Indexes". You may also be interested in this: https://gitorious.org/readynas/apache-configs

-Stefan
Avon_Fox
Aspirant
Jan 11, 2012
Thanks for the suggestion but sadly no good. I've just tested and it works fine (generates indexes) for shares that I make and enable http access for that don't have indexes.

It's just those that are sitting in the folder that I have set up in 'my-virtual.conf' that it doesn't work for. Is there something in httpd.conf that would conflict with how I've set up access to the /web/ folder?

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