Hi,

Today I've upgraded from 6.16 to 6.17 following the UPGRADE.txt.
After the upgrade non of the users, including the first created user (id=1)
can login. All the unauthenticated content works fine.

I get "You are not authorized to access this page".

Reverting back to the old site (6.16) everything works.

System is Centos 5.5
kernel: 2.6.18-194.3.1.el5xen
php-5.1.6-27.el5

best regards,

Giannis

Comments

webstylemedia’s picture

webstylemedia commented

Agree!
Guys, this is absolutely untested release.

Why it was released untested?

We updated website yesterday to new release and gone to home. In the morning we found that a whole night was a nightmare - no one was able to login.

Really shit.

Guys, please be more accurate.

Do better 100 time more tests before releazing it.

Release mean for me a version that must be used on live site.

Or do releasing of dev versions first.

I am sure I don't need to teach you guys.

Dries, ask all your acquia team to stop doing commercial support and put all power to drupal that we like.

D

:-)

Troodon’s picture

Troodon commented

Have you taken a look at this: after upgrade from 6.16 to 6.17, I can't login anymore

That is it may just be an issue with how you've set your $cookie_domain.

bilias’s picture

bilias commented

Clearing cookies from the browser fixed it.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Fixed
vinoth.3v’s picture

vinoth.3v commented

So we need to tell all the site end users to clear the browser cookies ???????????

Anjaro’s picture

Anjaro commented

Subscribing.

mcrittenden’s picture

mcrittenden commented
Title: You are not authorized to access this page after upgrade to 6.17 » "You are not authorized to access this page" after upgrade to 6.17
Component: other » user system
Status: Fixed » Active

This doesn't really seem fixed. Telling everyone to clear browser cookies isn't really a solution. Is that really all we can do here?

mcrittenden’s picture

mcrittenden commented

Looks like this is the issue that led to the cookie changes in 6.17: #458704: Don't automatically remove "www." from admin-set cookie domains.

And a possible fix: http://drupal.org/node/611920#comment-3110010

bradezone’s picture

bradezone commented

subbing. methinks this could be a major league problem for tons of sites.

bryrock’s picture

bryrock commented

subscribe

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Closed (duplicate)

This is actually a duplicate of #611920: Login issue. login does not work.

Davinia’s picture

Davinia commented
Version: 6.17 » 6.19

I just updated my drupalversion to 6.19 and I have the same problem. Please help? I've read and implemented the "solution" in the other issue topic but that doesn't work for me.

Ole Martin’s picture

Ole Martin commented

I have the same problem, went from 6.17 to 6.19.

vortexcentrum’s picture

vortexcentrum commented
Status: Closed (duplicate) » Needs work

Upgraded some 15 sites to 6.19 and one of them has this error. Clearing the cache does not work. They are all hosted on the same server.

Problem is in Firefox 3.6.3. Can get access in IE8.06.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Needs work » Closed (duplicate)

See #611920: Login issue. login does not work.

David Henry’s picture

David Henry commented

Quickly!!!!
in your settings change:

# $cookie_domain = '.example.com';

to:

# $cookie_domain = 'example.com';

This has worked for me after trying a lot of different things of which none worked.

Commenting it out is also recommended if that works for you.

The full skinny is here:
http://drupal.org/node/816998