When flushing all caches or any of the submenu caches (i.e. menu, theme) it redirects to home page with a 403 response. Access denied. You are not authorized to access this page.

Tested on clean install of drupal 7.39 on php 5.6.13.

The admin_menu URL is:
http://www.example.org/admin_menu/flush-cache?token=HcJYxXIxlhnRFGnZpiNQuwaRrxKK8GxT2r60ARJd3KI&destination=admin_menu/flush-cache

Nginx-1.9.4 Config.

...
location / {
	try_files $uri /index.php; # For Drupal >= 7
}

location @rewrite {
	rewrite ^/(.*)$ /index.php?q=$1; #Drupal
}
...

System Permissions

/sites/default/files is writable.
/tmp is writable

All admin menu settings are default.

I am pretty sure I a missing something, as I can't see how this issues has been overlooked for so long.

CommentFileSizeAuthor
Access_denied_Drupal_Fresh_Install_-_2015-09-24_23.38.16.jpg42.23 KBcj-a-min
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

cj-a-min created an issue. See original summary.

cj-a-min’s picture

cj-a-min CreditAttribution: cj-a-min commented
Issue summary: View changes
newmediaist’s picture

newmediaist CreditAttribution: newmediaist commented

Confirmed I previously experiencing the same problem - in my scenario it was related to the NGINX setup. I followed the "stock" NGINX setup listed at https://www.nginx.com/resources/wiki/start/topics/recipes/drupal/ , which caused the issue for me. Specifically, it was the line:

        fastcgi_param SCRIPT_FILENAME $request_filename;

I instead replaced it with the following:

    fastcgi_param  SCRIPT_FILENAME $document_root$fastcgi_script_name;

And the 403's went away.

truls1502’s picture

truls1502
he/him
Primary language Norwegian Bokmål
CreditAttribution: truls1502 as a volunteer and at SignWo AS commented
Status: Active » Postponed (maintainer needs more info)
Issue tags: +postponed2w

I am sorry for no reply until now.

There are many issues regarding this module admin_menu which is a bit difficult for us to follow up since some of the issues might be already outdated, or is already fixed by the module or any other modules or itself core which means that the problem might no longer need to be fixed.

We can see that the issue has been created for a few years ago, I hope it is okay for you that I am postponing the issue, and give you around two weeks. If you still face the problem, could you tell us the step by step when until you get the error message or what is frustrated you, and a list of modules you are using related to admin_menu and a screenshot that might help us? So it makes us easier to reproduce your issue.

However, after two weeks with no feedback - we will close this issue. So in case, you noticed it after the issue is closed, do not hesitate to reopen it like and fill information which is mentioned above.

So before giving us a feedback, do you mind to test it again with our latest 7.x-3.x-dev?

Thank you for understanding! :)

truls1502’s picture

truls1502
he/him
Primary language Norwegian Bokmål
CreditAttribution: truls1502 as a volunteer and at SignWo AS commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
Issue tags: -postponed2w

This issue has been automatically marked as closed because it has not had recent activity after the last post.

However, if you or someone is still facing the same issue as described to the issue, could you please to re-open the issue by changing the status of the issue, and add an explanation with more details which can help us to reproduce your situation.

Again, thank you for your contributions! :)