By ralph76 on

Access denied You are not authorized to access this page.

- is all i see, when i visit my Drupal site without logging in. I changed something in the settings i guess, but i don't remember what i changed.

The problem is that i have no access whatever page i click: faq, contact, about, ...

Can someone tell, how to get access for anonymous users again?

Cheers,
Ralph

Comments

sangamreddi’s picture

sangamreddi commented

Hi Ralph,

Wht version ur using if it's 4.6 check adminsiter>>access control and check node module access content box is checked for anonymous user.

Regards,
Sunny

ralph76’s picture

ralph76 commented

Yes, i'm using 4.6.1 and the box is checked - but still no access...

Cheers,
Ralph

Bèr Kessels’s picture

Bèr Kessels commented

Version, the exact path you try to visit, the modules installed, any third party moduls installed, themes you use. Please provide enough information for us to help you with your problem.
---
Next time, please consider filing a support request.

[Bèr Kessels | Drupal services www.webschuur.com]

ralph76’s picture

ralph76 commented

Drupal 4.6.1 default (no third-party-modules and no module settings changed), default theme, installed in a subdomain "drupal" in my domain web31.server-drome.info.

Cheers,
Ralph

sangamreddi’s picture

sangamreddi commented

Hi Ralph,

I got the same problem and noticed that my node_access table has been corrupted i restored it from backup now everything is fine. The reason mae be either the node_access table has not been installed properly or corrupted. Try to reinstall the table.

Cheers,
Sunny

conann’s picture

conann commented

I was just about to search about this problem, nodes are not available to anon users, site menu is available and taxonomy links are working but no content can be viewed. Home page is still the default though I have created a couple of hundred nodes.

Decided to do a little work on this before posting further if "administer nodes" must be on for anon to view nodes. I am using 4.6.0 and was hoping that the update would fix this.

Conánn

Sipefree’s picture

Sipefree commented

I had this problem when I installed first, and it boiled down to this for me.

When I was installing, I ran the database.mysql but got an error (I forget how, I think because I used a table prefix and didn't do them all) and it didn't create all the database tables, namely node_access.

What I would recommend is delete all your database tables and try again.

conann’s picture

conann commented

I would like to do this but I am a few 100 hours into node creation and starting from scratch is not something I would want to do. if there is a way of exporting and then reinstalling that would be OK

ralph76’s picture

ralph76 commented

Thank you to all for your help, but i dumped Drupal. As much as i would have liked to use it, i can't do anything with it, due to the error i get all the time (namely "Duplicate entry" - see other posting from me).

Will drop back here, when a new version is released and then give it another try.

Cheers,
Ralph

haleOnEarth’s picture

haleOnEarth commented

Unfortunately I had to dump drupal too, it's too bad but this thing is really a POS. Waaay too inconsistent. For the last half of 2005 I was able to set up drupal sites rather routinely, now all of a sudden, the damned thing won't work on any servers I set it up on. I've wasted soooo many hours working with web host support staff, consulting books on my own development servers, forums, ad infinitum. Either themes are conflicting with PHP, or access is constantly being denied for one reason or another. Sometimes the old adage "you get what you pay for", rings loud and clear. I've already lost way too many hours that I'll never get back. Best of luck to the rest of you!

harry slaughter’s picture

harry slaughter
Location Omaha NE USA
commented

Debugging any web application can be painful. Drupal is not an exception.

There's a reason for every problem.

I've never once had a problem with a properly installed instance of a stable version of Drupal not working. That's not to say it can't be easily broken after it is installed.

Things that can render drupal broken:

- running a non production release of drupal
- (untagged) third party modules
- "playing around" with the drupal admin interface
- messing with drupal's db

you're going to run across these same types of problems with any CMS. at some point you're going to have to stick it out and debug your problem instead of switching to a new CMS.

--
Drupal tips, tricks and services
http://devbee.com/ - Effective Drupal

--
Devbee - http://devbee.net/

harry slaughter’s picture

harry slaughter
Location Omaha NE USA
commented 
INSERT INTO users (uid, name, mail) VALUES ('0', '', '');
INSERT INTO users_roles (uid, rid) VALUES (0, 1);
INSERT INTO node_access VALUES (0, 0, 'all', 1, 0, 0);

will either return 'duplicate entry' warning (which is OK) **or** fix your problem.

--
Drupal tips, tricks and services
http://devbee.com/ - Effective Drupal

--
Devbee - http://devbee.net/

webcomm’s picture

webcomm commented

This fixed the problem for me in Drupal 5...

INSERT INTO users_roles (uid, rid) VALUES (0, 1);
INSERT INTO node_access VALUES (0, 0, 'all', 1, 0, 0);

Hopefully that won't break something else.

-Ryan

chrispeat’s picture

chrispeat commented

I hadnt realised that node_access also added a new set of permissions on nodes, so had to enable that. Fairly obvious really...