8000 [BUG] Login fails after update to octoprint 1.8.3 · Issue #235 · OctoPrint/octoprint-docker · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[BUG] Login fails after update to octoprint 1.8.3 #235

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom
Open
Sroose opened this issue Sep 22, 2022 · 4 comments
Open

[BUG] Login fails after update to octoprint 1.8.3 #235

Sroose opened this issue Sep 22, 2022 · 4 comments
Labels
bug

Comments

@Sroose
Copy link
Sroose commented Sep 22, 2022

Describe the bug
After letting octoprint update itself to the latest version, 1.8.3, logins fail (http 403)

It seems to be related to haproxy an security changes dicussed at OctoPrint/OctoPrint#4645

Container Details
"2022-08-09T12:33:57.320Z"

To Reproduce

  1. login to to octoprint web gui
  2. allow updating to 1.8.3
  3. try to login again after it restarts
@Sroose Sroose added the bug label Sep 22, 2022
@DevAlphaKilo
Copy link
DevAlphaKilo commented Oct 6, 2022 •
edited
Loading

This issue is also in image 1.8.4 and I'm having the same problem. I do not think this is related to the haproxy.

Any recommendations for fixes?

Steps I did:

  1. Working as expected
  2. docker-compose down
  3. docker-compose pull (octoprint:latest)
  4. docker-compose up -d
  5. WebGUI Login Fails
    4.1. Login to docker container docker exec -it {container_id} /bin/bash
    4.2. Check user list octoprint user list (0 users registers in the system)
    4.3 View docker container volume contents cat /octoprint/octoprint/users.yaml (Shows me [admin] and single [user] account)

When executing octoprint user add bob the new user is added to /home/root/.octoprint/users.yaml file.

@drewgates
Copy link

Same problem. I've been poking at this for about a week now with no success.

@darsys
Copy link
darsys commented Dec 17, 2022

I had the same issue. I am using docker-compose and the fix was to docker-compose down and up. I know this sounds too simple but it worked for me. I had restarted the container via docker several times.

@LongLiveCHIEF
Copy link
Member

One thing to note is that when using octoprint cli in this image, you have to pass the --basedir /octoprint/octoprint option so it looks in the correct directory for octoprint configurations and data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@darsys @LongLiveCHIEF @drewgates @Sroose @DevAlphaKilo
0