Can't log in - ISSUE FULLY FIXED NOW?

Is RateBeer stuttering to a slow and painful death? I had this issue, but able to rate again. For now.

1 Like

It does feel like it may not be functional much longer… then again how many times have i said that??

Tried to log in, nope. Time to update my last back up data set!

1 Like

Just use any part of the old site, like this RateBeer.com -- Login to log in until the cookie issue is fixed.

1 Like

Just to be clear though … this logs you in to search and rate but still doesn’t give ‘me’ the ability to look at community or latest activity

For whatever reason we aren’t all suffering from exactly the same issues

1 Like

Strangely, I’m fine on all fronts apart from not being able to use ‘Most Breweries Rated’ option.

<*))))))><

I can’t get in via places, add places anymore

Simply clicking on places gets the ROBOT now

Luckily I’d left a random window open on Firefox, logged into RB, that I’m able to use

Of all the bollocks we’ve had on the site in the past few years this is the worst technical episode

Be a lot more fuss if everyone was affected like me

1 Like

I reset my password the other day and everything is currently working as normal. Prior to that all I could do was view the forums.

1 Like

I tried a password reset earlier in the week … maybe give that another go

1 Like

And a reset is only possible via ‘account settings’ ?

Which I just tried and yes … ROBOT

1 Like

What is the deal with this website? I registered some months ago. I was worried that this could be a one-man army, and when the moment comes, this website will stop working and dissapear, specially seeing the eternal notification about 2020’s beer awards. Seeing the info about this website being owned by AB InBev was part of why I picked this db over other alternatives…

After the search bug and now the login bug, I think time has come to download my ratings in csv and move on to greener pastures. Thanks for the fish and so on… Take my advice and backup your data. Doesn’t seem like this website is going to have a bright future…

Thank you for your participation and your opinion. We who still care are sad to see new users go, but, honestly, this site has weathered worse dramas than this issue, and while we certainly back up our ratings regularly, a lot of us still don’t see a huge need to panic. It’s an annoyance, but an annoyance with some semblance of a plan of being resolved, like the search bug was resolved quickly. The site is certainly a bit dead in the water now but there are still plenty willing to keep it up and running.

8 Likes

Going through older pages appears to be the trick- thanks everyone!

1 Like

Also, we had a little intervention, and Joe fixed @Theydon_Bois ’ other issues. :smiley:

If someone else’s experiencing it - robots in places where there definitely shouldn’t be any and only while you’re logged in, ping me, it should be an easy fix for Joe!

It should only affect some people whose accounts were split in two accidentally.

3 Likes

Let’s give it a few weeks. :joy:

1 Like

Interesting that there are 62 CaskExports users numbered CaskExports1 (since Oct 2017) to CaskExports62 (since Nov 2022). I didn’t realise it was such a popular nick.

1 Like

this is working for me, thanks! ‘legacy log in’
https://www.ratebeer.com/add-place

3 Likes

I FINALLY got in, so I’ll share how I did :

Cleared all ratebeer cookies from my browser

went to www.ratebeer.com/Places/

THIS IS THE IMPORTANT PART

I clicked the blue add a place button

Then a login prompt showed up

And I could log in

What I had tried earlier, that didn’t work was to click the login button on the places page. That got me a login prompt and after entering name and pass, I got a cloudflare error (tried on 3 computers, two networks, two countries etc. etc. no luck)

2 Likes

Finally managed to get in this morning after much faffing, had about 20 goes at differing entry points, still getting the robot when I try some sections of the site. Hopefully, when I get some time, I can download my data.

I’ve been okay for the last week or so, until the next issue where we end up having to use a weird workaround.