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

WhoCares_
Mentor
Feb 26, 2012
Strange, didn't happen for me. Will investigate. As to the "easy Apache setup": Well, if you want a real Linux you've got to build your own box. Apparently the ReadyNAS (and other NAS boxes as well) wasn't built with the idea of users running web servers in mind. That's a design decision and unfortunately it's not that easy to revert. Anyway, I'll look into this, maybe it's just a small problem with the config I posted on Gitorious.

-Stefan
WhoCares_
Mentor
Feb 29, 2012
My bad. I just checked with my local install and found that I hadn't checked in a lot of changes to the repository on Gitorious. Please revisit the repo and see whether the new version (x86, read CHANGELOG) works for you.

-Stefan
ericclaeren
Aspirant
Feb 29, 2012
Thanks Stefan, I will look into it this weekend.

You're right about a plain linux machine. I thought running a webserver on this, quite powerful and machine, would be a piece of cake. Since it was just linux, but installing any software directly on it is a pain in the...
You can't update or upgrade anything easily because it's so heavily modified. Well lesson learned :D

Thanks for your help
WhoCares_
Mentor
Feb 29, 2012
K, gives me some more time to push the ARM changes, too ;)

-Stefan
ericclaeren
Aspirant
Mar 04, 2012
Hi Stefan,

Thanks dude! It works! Used the latest git for x86.

I have added my own line to the http.conf for my own vhosts, didn't want to mess around in addons dir for my sites.

# Include sites that defines it's own vhost
Include /etc/frontview/apache/sites/*.vhost

For other users: My default vhost file now looks like this. It probably could need some extra tweaking, but it works for now.
I put my sites in a shared directory called www so I can access the files easily within my network.

Location: /etc/frontview/apache/sites/example.vhost

<VirtualHost *:80>
ServerName www.example.com
ServerAlias example.com
DocumentRoot /www/example

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

<Location />
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>

Thanks for your help!
WhoCares_
Mentor
Mar 04, 2012
You shouldn't place your web roots (/www/example in your case) on the main OS partition. A better approach would be to place them in a directory below /c like /c/www/example or the like.

-Stefan
ericclaeren
Aspirant
Mar 04, 2012
It isn't (think so) /www/example is in my case /c/www/example. I created a shared folder called 'www' via readynas frontview. Normally on linux I would use /var/www, would that be a better folder?
WhoCares_
Mentor
Mar 04, 2012
No, using /www/example is fine as long as it is as you describe above. On the ReadyNAS /c and below is the big storage space and pretty much everything else is the OS partition (unless symlinked to something under /c of course).

-Stefan
ericclaeren
Aspirant
Apr 26, 2012
Hi Stefan,

Just installed the 4.2.20 firmware update, now my frontview is really really dead. Did you encounter this problem too?
Can't get apache started, while doing: apache-ssl -f /etc/frontview/apache/httpd.conf

I received the following errors:

(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

Any Idea, where this is coming from? Haven't changed anything further to my Nas.

Thanks!
WhoCares_
Mentor
Apr 26, 2012
This means that something already is sitting on port 80 - which on the ReadyNAS should be only Apache. What's the output of
ps ax | grep apache

Additionally you may want to try
apache-ssl -f /etc/frontview/apache/httpd.conf -k restart

and see whether this revives FrontView.

-Stefan

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