opf
Invalid user or password or the account is blocked due to multiple failed login attempts. If so, it will be unblocked automatically in a short time.
git clone https://github.com/opf/openproject-deploy --depth=1 --branch=stable/14 openproject OS: Ubuntu22 Hi,When I finished installing with docker,Thd default Username: admin,Password:admin ,But it says the wrong thing Invalid user or password or the account is blocked due to multiple failed login attempts. If so, it will be unblocked automatically in a short time.
I installed this on different machines,always the same!
I am facing the same issue, I installed open project using the steps mention in Docker compose on the GitHub repo but everytime I used the login credentials it show the message
I got the same problem. When I logged the seeder container, I found "rake aborted!
Errno::EACCES: Permission denied @ dir_s_mkdir - /var/openproject/assets/files (Errno::EACCES)".
So, I changed the owner of $OPDATA directory in the host.
chown 1000 /data/openproject/assets
Then up docker compose, logging with default password will be succeeded.
If you change in the .env file the TAG directive from TAG=14-slim to TAG=14 the admin user is properly created.
The OpenProject slim container runs on UID 1000.
So you need to make sure that the path you mounted to your docker container has the right ownership.
If you are using the defualt from the .env.example value this is /var/openproject/assets.
You can use the following command to set the right ownership:
sudo chown 1000:1000 -R /var/openproject/assets
I added a PR to add the right instructions to the documentation
Unfortunately I saw this issue after digging for a lot of time to understand why the login as admin was not possible after a fresh install. The description here by @tiroessler made clear the problem and maybe the fact that:
The OpenProject slim container runs on UID 1000. So you need to make sure that the path you mounted to your docker container has the right ownership.
So maybe this could be added to the documentation to let the user understand why chown 1000:1000 has to be used?
Could this maybe be solved / extended by adding user: "${UID}:${GID}" to each service inside the docker-compose.yml file and let the admin set those values in the .env file? See https://blog.giovannidemizio.eu/2021/05/24/how-to-set-user-and-group-in-docker-compose/
Or does changing the user has an impact on other functions of the containers?
The install instructions with Docker Compose have been updated with the commands to create the assets folder and chown to the correct UID.
However, after following this, I still am getting the same error when trying to log in with the default admin/admin. To verify, I checked and verified that the /var/openproject and /var/openproject/assets folders are both owned by the user account I'm using to run the container.
The only other option I could find was this comment from mariogalan suggesting removing the -slim from the line in .env. In my file this meant changing "TAG=15-slim" to "TAG=15". After shutting everything down, logging out and back in, then rebuilding, I was able to login with the admin account and proceed.
To remove the "-slim" helped. But in addition I needed to create the "<myPath>/openproject/assets/" directory before run docker compose up, because my setup does not use the default paths of .env-example.
With these two steps and let the setup process run for around 10 min before open IP/URL in Webbrowser first time... (I guess some containers restart in between while first run for setup?) It worked.
