[Bug]: Login / logon not working with production docker releases [Solved]

[matteof]

Is there an existing issue for this?

• I have searched the existing issues

Description

A nightly update of AppSmith docker executed with the suggested command:
docker-compose pull && docker-compose rm -fsv appsmith && docker-compose up -d
has broken the login page.
The users already logged in did not have issues for days, but new user or user which needed to logon faced where presented a page saying only:
"Unauthorized".

We decided to freshly install docker v1.65 and it has the same issue, we tested docker appsmith v1.64 and again the issue was present.
([Edit] Some user report that downgrading to v1.64 works fine, but v1.65 gives the issue)

Luckily enough, v1.63 does not have the error: analyzing the release notes in v1.64 a login feature was implemented (#37292).

There is already another issue about this error (#39983), but I wanted to share the analysis done and the regression test we have performed.

Steps To Reproduce

1. Install v1.64 or v1.65 using the instruction in (https://docs.appsmith.com/getting-started/setup/installation-guides/docker)
2. Go to the login page
3. The page gives "Unauthorized"

Public Sample App

No response

Environment

Production

Severity

Critical (Broken Production apps)

Issue video log

No response

Version

docker 1.65, docker 1.64

[aledonati]

Same issue here

[iSlans]

yeah we got this problem too :c

[andreadapisa]

Same issue: I'm "Unauthorized" even though the credentials are correct and redirect to the login page.

[thebigpotatoe]

Same here

[matteof]

Please note, I went in Discord support and there are 3 users reporting the same issue in the last 2 days.
Some user report that downgrading to v1.64 works, so it might be a v1.65 issue.

[chrishodgkins]

Downgrading to 1.64 resolved it for me

[antlevy]

V1.64 didn't work for me but v1.63 solved the issue.

[CoelhoNL]

I'm facing the same problem. Downgrading to v1.64 worked to me.

[cayetano]

Upgrade to last version work now!!!!

[oleombruni]

I can confirm that upgrading to v1.66 solved the issue on our instance.

[matteof]

I cannot change status, but 1.66 solves the issue.