We discovered this morning that Filebrowser has stopped allowing downloads for one of our Nodes:
http://www.broomfieldsoccerclub.org/coaches_tools
I have compared this Node to the settings on another one that also uses Filebrowser, but is still working:
http://www.broomfieldsoccerclub.org/fields_sched_rec
The settings on the Nodes are identical. I've checked Home › Administer › User management > Permissions and everything looks okay. The Unix permissions on the server directories themselves are the same for directories under both Nodes (744 for the directories, 666 for the files inside the directories).
The only difference seems to be the Node that isn't working exposes multiple folders which contain files rather than simply exposing a set of files within a single directory
I am using 6.x-2.0-rc13 with Drupal core 6.24. The site also uses Boost, but not sure that should matter.
Here's the exact error:
Access denied
You are not authorized to access this page.
Comments
Comment #1
Nicolas Georget commentedThat's weird! To debug:
Comment #2
Nicolas Georget commentedBy the way, Are you sure the both node have the same "private / public" download setting?
Comment #3
davidafuller01 commented1. I rebuilt the permissions, but it didn't fix the problem.
2. I don't have access to the Apache logs (at least I don't think so). The site is deployed on a shared server with a major hosting provider.
3. The site uses Content Construction Kit (CCK) 6.x-2.9 and node privacy byrole 6.x-1.6 amongst many other modules. These modules have been in use for long time, but both were updated in the past 4-6 weeks.
4. Not sure I understand this one. I should look up in MySQL the path Filebrowser has assigned to see if it matches the "real" path?
5. Both Nodes are set for "Direct download"
Here is the HTTP error I'm getting for the example file you asked about:
Request URL:http://www.broomfieldsoccerclub.org/filebrowser/download/13959
Request Method:GET
Status Code:403 Forbidden
BTW... Filebrowser is working as expected for authenticated users. Just anonymous is broken.
Comment #4
Nicolas Georget commentedDo you use SSL for the authenticated users?
For my point #4, forget it because it works for the authenticated users. So based on that:
Are you sure there UNIX perms are recursive? 744 for folders and 666 for files.
To be sure if it's Drupal or Apache that send a 403, can you try to with your browser to access directly to your file:
Of course my direct link is not correct and depends on where your file is hosted on your server. And
Comment #5
davidafuller01 commentedI don't have SSL running.
I checked the directory to see if it was 744 and all the files within the directory to see if they were 666 and all was well. I've looked around and found some directories (directories not connected to a Filebrowser Node) and many are 755. I have changed the directory for this Node to 755.
The direct URL to the file works, but it wasn't working until I changed the permissions on the file's directory to 755. When it was 744, I was getting Error 404.
So, let me replay where we are:
What are we missing?
Comment #6
davidafuller01 commentedI couldn't wait any longer to figure out why this was broken, so I have re-designed the site to work around it.
Comment #7
Nicolas Georget commentedWhat did you do by "re-designed" ?
Comment #8
davidafuller01 commentedI removed the page which contained a directory of sub-directories. It is now a links page which sends users to other pages each consisting of one of the sub-directories. All seems to be working fine now and I don't mind the new structure as it allow me to expose more depth in the menus.
Comment #9
Nicolas Georget commentedOK then!