Users cannot log in with "Drupal\Core\Http\Exception\CacheableAccessDeniedHttpException: The 'access user profiles' permission is required and the user must be active"

Ran into this locally - I was using `drush uli` to jump into a local copy of the site. Just for context, I was using Docksal locally, my site was fully functional on Pantheon, no issues using `drush uli`, but `fin drush uli` (Docksal's implementation to run a drush command on my container) on my locally was sending me to an "Access denied" page - I cleared cookies for my local site, in this case `mysite.docksal.site`, and voila! I am back online. I understand this probably won't help a ton with an actual fix, but my primary hope here is to aid any future devs that might have found their way here, and offer a workaround solution.

This is a really bad way of notifying the admin of permission errors, experienced the same today with group and domain access drupal 10 website.
After configuring the permissions properly no more errors shown.

Related #3213029 #3251815 #3168773 #3166208 #3166208

We're facing this issue too with one of our Drupal 7 to Drupal 11.2.2 migrated production site.

Locally there was no issue, all migration steps were executed well. Even for the same site, when it was migrated to UAT release we haven't notice this "Access denied" issue. But finally, when the UAT site is configured with production domain configuration with Apache, All of the site users including the Administrator, started facing the login issue as:

Path: /user/admin?check_logged_in=1. Drupal\Core\Http\Exception\CacheableAccessDeniedHttpException: The 'access user profiles' permission is required. in Drupal\Core\Routing\AccessAwareRouter->checkAccess() (line 114 of /[PATH]/web/core/lib/Drupal/Core/Routing/AccessAwareRouter.php).

After all possible tweaks with Apache site configuration, the issue haven't resolved. But when I checked the cookies in the browser (which is facing this issue), I found that there are two cookies with the same name exists in the list.

If one session key name is edited and renamed, the site login allowed with no issue, but if the same renamed key is reverted, I again started facing the "Access denied" issue.

Additionally, When I tried to login to the same site in a different browser where this site was never accessed, I faced no issue of "Access denied". Even if we try to login with Incognito mode, the login still works.

So, same as #17, clearing the cookies solved the problem, but that is only for us. lots of our site users still facing the "Access denied" issue and we can't yet fix it, because we're still not sure its a Drupal Core issue or the cookie? as our other migrated site with the same Drupal version never faced this problem.