403 error with new websites.

[till]

Which setting do you use in system > server config > web > security level? The recommended setting is high.

And which linux user and linux group is used for this website?

[otacon]

Security Setting Is "High"

User = web15
Group = client0

[otacon]

Ok, so as I am stumped as to why this is happening I have done a bad work around to fix the issue.

in the .vhosts I changed the 403 error path to index.html. This restricts the users to having this exact file name.

I will post an answer as soon I discover it.

[otacon]

Alright it has been long enough for me to be fed up with all this troubleshooting so instead of me just doing random things I find on the web I am going to have to do this in a more intelligent manner.

ok So I need to start off by listing all the possibilities of a 403 error on a web site then from that list systematically rule out each issue until I get to the root cause.

I need help with the first step of this process. My current list of possible causes is as follows:

1.Site is password protected.
2.Wrong Group for access
3. Wrong username for access
4.The website may be configured so as to disallow all attempted requests for directory listings


When accessing the directory from the internet what user and group is used by the user to access those files? Is it client24:web52 *example*?

Also I am having no issue when I create a website through the control panel. Does the API do this process manually or does it use whet ever the control panel uses? if it uses the same script then I would have to assume that the problem is in my registration script.


Thank you for your help and I hope I can figure this out soon,
otacon

[till]

When accessing the directory from the internet what user and group is used by the user to access those files? Is it client24:web52 *example*?

Thats depends on the file type that you access and the options that you have set in the website. E.g. html files and images are accessed by the apache user while php scripts run under the web user when you have suexec enabled.

Also I am having no issue when I create a website through the control panel. Does the API do this process manually or does it use whet ever the control panel uses? if it uses the same script then I would have to assume that the problem is in my registration script.

Then its most likely a problem with your script. ISPConfig uses the same code to create a website wether you use the ispconfig interface or the api.

[otacon]

Originally Posted by otacon

error.log

[Thu Mar 24 19:23:05 2011] [error] [client 98.226.168.246] client denied by server configuration: /
[Thu Mar 24 20:26:32 2011] [error] [client 98.226.168.246] client denied by server configuration: /
[Thu Mar 24 21:24:36 2011] [error] [client 98.226.168.246] client denied by server configuration: /
[Thu Mar 24 21:24:36 2011] [error] [client 98.226.168.246] File does not exist: /var/www/testing2.remcycle.net/web/favicon.ico, referer: http://testing2.remcycle.net/

testing2.remcycle.net/index.html works.

I guess I could fix it with an htaccess file , but I would prefer to figure out why the directory isn't forwarding to index.html.

should these errorlogs be saying client denied by / "root"? Why would it be trying to access root?

Is this normal or should it be /var/www/testing600.remcycle.net/web?



-----------------------------------------------------

Ok I think that was the problem. I added


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


to testing600.remcycle.net.vhost and now it works.

Now I have to find out why it needs to go to the root directory.

Will adding this to the vhost create a security risk?


------------------------------------------------------------------

another update. I have found the issue inside the vhost.

in the vhosts that are created through API

PHP Code:

    RewriteEngine on
    RewriteCond %{HTTP_HOST}   ^test.remcycle.net [NC]
    RewriteRule   ^/(.*)$ /$1  
    RewriteCond %{HTTP_HOST}   ^www.test.remcycle.net [NC]
    RewriteRule   ^/(.*)$ /$1 


is added once this is removed the domain works perfectly. I am not sure what this means, but I will be doing a little googling to find out.