We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug I just updated my test instance from 2.33.0 to 2.36.4 and I can't login anymore.
To Reproduce Steps to reproduce the behavior:
Expected behavior To login :)
Screenshots N/A
Please complete the following information:
Debug/logging information Read here how to log
[2024-07-05 08:21:50.745][2fd74ed8] SERVICE[WARNING]: InvalidToken[101] #0 /srv/www/vhosts/mydomain.tld/htdocs/webmail/snappymail-test/snappymail/v/2.36.4/app/libraries/RainLoop/Service.php(132): RainLoop\ServiceActions->ServiceJson() #1 /srv/www/vhosts/mydomain.tld/htdocs/webmail/snappymail-test/snappymail/v/2.36.4/app/libraries/RainLoop/Service.php(14): RainLoop\Service::RunResult() #2 /srv/www/vhosts/mydomain.tld/htdocs/webmail/snappymail-test/snappymail/v/2.36.4/include.php(136): RainLoop\Service::Handle() #3 /srv/www/vhosts/mydomain.tld/htdocs/webmail/snappymail-test/index.php(11): include('...') #4 {main} [2024-07-05 08:21:50.948][27b21718] SERVICE[WARNING]: InvalidToken[101] #0 /srv/www/vhosts/mydomain.tld/htdocs/webmail/snappymail-test/snappymail/v/2.36.4/app/libraries/RainLoop/Service.php(132): RainLoop\ServiceActions->ServiceJson() #1 /srv/www/vhosts/mydomain.tld/htdocs/webmail/snappymail-test/snappymail/v/2.36.4/app/libraries/RainLoop/Service.php(14): RainLoop\Service::RunResult() #2 /srv/www/vhosts/mydomain.tld/htdocs/webmail/snappymail-test/snappymail/v/2.36.4/include.php(136): RainLoop\Service::Handle() #3 /srv/www/vhosts/mydomain.tld/htdocs/webmail/snappymail-test/index.php(11): include('...') #4 {main}
Additional context I also notice the login screen changed from asking Email/Password to Email/Passphrase. Did I miss something in a release note?
The text was updated successfully, but these errors were encountered:
There are 3 InvalidToken errors:
You probably hit no. 1 so try to clear browser cookies/cache of that website and try again.
Sorry, something went wrong.
Improved InvalidToken handling for #1653
288ff23
I tried 3 browsers. Normal and in Private mode. None work with 2.36.4. The log just throws this error.
Continued at #1706
No branches or pull requests
Describe the bug
I just updated my test instance from 2.33.0 to 2.36.4 and I can't login anymore.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
To login :)
Screenshots
N/A
Please complete the following information:
Debug/logging information
Read here how to log
Additional context
I also notice the login screen changed from asking Email/Password to Email/Passphrase. Did I miss something in a release note?
The text was updated successfully, but these errors were encountered: