AH01797: client denied by server configuration since DA update to 1.44.1

dmacleo

Verified User
Joined
Jun 21, 2012
Messages
653
have an owncloud site running that was working fine this morning, I did the DA update to 1.44.1 and now client sync to server gets AH01797: client denied by server configuration error.
ownership and permissions have not changed that I can see and I do not see any
<Directory NAME>
Order allow,deny
Allow OR DENY from all
</Directory>


type of statements on the httpd conf files.
I have rebooted server, done a rewrite conf in custombuild and did a build php n also.
still same errors.
I disabled the firewall to make sure it wasn't that also.
the only change done between working site and non working site was the DA update.

anyone have any ideas why this happens now?
 
hmmm httpd-directories.conf uses
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>

statements however for apache 2.4 these are wrong.
should be something like
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
</Directory>
but still, the real question is why a DA only update caused issues
 
odd, look slike it updated to apache 2.4.7 during the process, wonder if thats the issue
 
ok for some reason in \conf\extra\httpd-directories.conf I had to comment out these lines
<LimitExcept GET POST OPTIONS PROPFIND>
Order deny,allow
Deny from all
</LimitExcept>
and I don't know why I needed to do this after just a DA update. I also don't know the repercussions this may cause for other sites, am looking to see if I can do it through htaccess
 
Updating DirectAdmin shouldn't update Apache. Are you positive something else didn't update Apache?

Jeff
 
Updating DirectAdmin shouldn't update Apache. Are you positive something else didn't update Apache?

Jeff

I was on 2.4.6 (I had actually checked earlier that day) and all I did was do the DA update.
I cannot explain it but the httpd2.4.7 files in custombuild folder were timestamped about 2 minutes after I clicked the update button in DA.
doing rewrite conf shoudln't have done this, and I've never seen build php n do it so I cannot explain it.
as far as I can tell I am not having any issue from commenting out those lines.
 
Am I misunderstanding something? updating files in custombuild shouldn't change your running copy apache version. Or any configurations in any running system.

Jeff
 
nope you are not misunderstanding.
you are correct (as far as I know) it shouldn't change it.
yet it did.
and I cannot explain it. nobody else has access either. oddest thing.
is it possible I somehow caught the update server at just wrong time? can't see how that would matter but I also could not find any evidence of anything else driving this.
now I just updated someone elses DA server (albeit on vps) and this did not happen. since there were no sites on server I could take the chance and see if it happened there so I followed same procedure and had no issues.
really this is more of a curiosity than an issue, because I would have updated to 2.4.7 within hours anyways once I made sure everything was ok after update.
 
have an owncloud site running that was working fine this morning, I did the DA update to 1.44.1 and now client sync to server gets AH01797: client denied by server configuration error.
This could simply be because you did something new in the owncloud sync folder, like creating a folder or moving a file.
The owncloud desktop client cannot work properly with the default DA config.

Commenting out the line like you did puts your whole server at risk. There are known htaccess attacks which can exploit the hole you've just created.
 
Back
Top