Enabling .htaccess

That certainly provides the added benefit of not worrying about forgetting to chattr when you do a system upgrade. I wonder if an addin could automate this.....

for me everything in /etc/frontview/apache/addons/ will not be overwritten by firmware upgrade so if you put you conf file in this directory it should be ok :)

dont know is file in this directory are read in [A-Z] order so call it zzzzzz.conf :P

Hi all, I've been having the same problem as the first post in this thread. I believe I have followed the subsequent advice but I am getting nowhere.

I am basically trying to setup a virtual host, and have created a share for this called /gbdev

I have created an individual conf file for this and placed it within the /etc/frontview/apache/addons directory

The contents of which are:

<VirtualHost *:80>
        ServerName <sub_domain+my_domain_here>
        SSLEngine off

        DocumentRoot /gbdev

        <Directory />
               Options All
               AllowOverride All
               Order allow,deny
               Allow from all
        </Directory>
</VirtualHost>

The site works fine as long as I don't have "RewriteEngine on" in the .htaccess file. As soon as I turn it on I get a 403 Fobidden error. The following appears in the apache error log:

[error] [client <my_ip>] Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that RewriteRule directive is forbidden: /gbdev/

Firstly, to even get this close to working I had to comment out the existing VirtualHost in the /etc/frontview/apache/Virtual.conf file otherwise I would get redirected to the /shares folder everytime I accessed the domain... not helpful. This may be where I started to go wrong but it doesn't seem to be the problem to me.

I also checked the /etc/frontview/apache/Shares.conf file but found mine is empty... So surely nothing is being overridden?

Right now I'd appreaciate a little help/advice and would be happy to provide more info if needed.

Thanks in advance,
Wazz

I read the posts regarding redirecting http requests on ReadyNAS. I'm trying to do something similar, I want to redirect http requests to https. Specifically requests to my share /webroot, /web and /media.

Question: where should I create the .htaccess file? In the root of each share, or somewhere else? All my shares are listed in Shares.conf (where I will set Options All instead of Options Indexes). I have found general examples on how to redirect from http to https, so what is missing is where to put that code, where do I create .htaccess?

Hello,

i found the solution on this site: http://www.get-the-solution.net/index-1 ... S---R.html
Its in german but i try to translate it:

Alias /www /c/www

<Location "/www">
  Options Indexes FollowSymLinks SymLinksIfOwnerMatch
  Order allow,deny
  Allow from all
</Location>

You have to copy this code into /etc/frontview/apache/httpd.conf

/www is used in this example as webfolder where all webpages are stored in. So you have to adjust the code to your webfolder. Thats it. Have fun.

greetings

Hey guys,

I'm currently hosting wordpress on my ReadyNas Duo and the performance is terrible. I'm trying to install the super cache plugin however it requires permalinks to be active however after enabling this I get 403 errors and can't access it.

I'm about to add the below to but I'm not sure how to change the following. The location of wordpress on the NAS is /c/website/test.

Would the following be correct?

Alias /website/test /c/website/test

<Location "/website/test">
  Options Indexes FollowSymLinks SymLinksIfOwnerMatch
  Order allow,deny
  Allow from all
</Location>

Any advice would be greatly appreciated :D

Hey,

I have come back to this a year later as I gave up on it.

Is anyone able to assist with the above as it doesn't appear to have worked.

You can call the location from the config above with http://youripadress/website/test

Maybe you also want check also the other configs in /etc/frontview/apache/addons/.

dthrevan wrote:
Alias /website/test /c/website/test <Location "/website/test"> Options Indexes FollowSymLinks SymLinksIfOwnerMatch Order allow,deny Allow from all </Location>

This looks almost correct but you may need to add a '+' sign in front of Indexes, FollowSymLinks and SymLinksIfOwnerMatch. Not sure about the correct syntax in a Location block but iirc you also need an "AllowOverride FileInfo" statement in there. Also, if you only want to enable .htaccess processing, you may only need the +FollowSymLinks option.

-Stefan