portainer: Unable to login in 2.29.1

Before you start please confirm the following.

Problem Description

Unable to login after Docker image upgrade

Expected Behavior

Fill the login form, click on login button to login successfully.

Actual Behavior

To successfully be able to login

Steps to Reproduce

  1. Pull Latest Docker Image portainer/portainer-ce:2.29.1
  2. Run the Docker image: docker run -d -p 9010:9000 --restart always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data --name portainer portainer/portainer-ce:sts
  3. In the Browser open the address http://localhost:9010/
  4. Fill the Login Form and click on Login Button

Portainer logs or screenshots

https://github.com/user-attachments/assets/ec29c0da-07dd-4a40-9d7b-8737df04abcb

Portainer version

2.29.1

Portainer Edition

Community Edition (CE)

Platform and Version

Docker version 28.1.1

OS and Architecture

Arch Linux

Browser

Chrome 135

What command did you use to deploy Portainer?

docker run -d -p 9010:9000 --restart always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data --name portainer portainer/portainer-ce:sts

Additional Information

  1. Also notice in the Browser Dev Console error http://localhost:9010/locales/en-US/translation.json 404 (Not Found
  2. Downgrading to 2.29.0 fails to run with this error FTL github.com/portainer/portainer/api/cmd/portainer/main.go:346 > The database schema version does not align with the server version. Please consider reverting to the previous server version or addressing the database migration issue. |

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 25 (2 by maintainers)

Most upvoted comments

As noted in - https://github.com/portainer/portainer/issues/12665 We are aware of an issue in 2.29.1 which causes the Forbidden - origin invalid we are looking to release a fix ASAP

Given the deltas from 2.29.0 to 2.29.1 are mostly CVE fixes, and the error is about forbidden origin, I wouldn’t be at all surprised if this is related to one of the CSRF CVE fixes?

You’d be right. We updated a third-party library in order to resolve the CVEs, and unfortunately that library update also resulted in this error occurring. Our team are currently working on a fix as their top priority, and while I can’t guarantee a release time we’re aiming to push it out as soon as possible. In the meantime you can roll back to 2.29.0 by restoring the database backup that is taken before Portainer is updated (this can be found at /backups/portainer.db.bak - stop Portainer, back up the existing portainer.db file, and replace it with the portainer.db.bak file - remember to change the extension - then start Portainer again with the 2.29.0 image).

We’ve just released 2.29.2 which should resolve this issue. Those affected, are you able to update and confirm this is now resolved? Remember to take a backup first!

Yep, doesn’t work, get a failure. As others said, nothing seems to work stack-wise (start/stop/update etc). Update has bricked all useful functionality. Don’t understand how this got through QC…

I have opened a separate ticket for the update stack issue. https://github.com/portainer/portainer/issues/12665

For those of you who had this issue and then resolved it with deleting cookies, have any of you tried updating a stack since then?

Yep, doesn’t work, get a failure. As others said, nothing seems to work stack-wise (start/stop/update etc). Update has bricked all useful functionality. Don’t understand how this got through QC…

@TinoKossmann yes confirmed, deleting the cookie solves the login problem,

but nothing seems to work (starting/stopping a stack, delete an image, delete a volume)


Start a stack fails with the error Forbidden - origin invalid

Image

Same here, you can solve this by delete cookies… but than nothing else works. Start a stack, create a new user, … everything fails with an error (but without logging (debug)).

Docker running on Debian 12, portainer-ee (!) 2.29.0 worked, 2.29.1 won’t.