What is uername and password?

[zinwelzl]

Docker installation, works great.

https://github.com/pablosnt/rekono/blob/main/docker/README.md#initial-rekono-user

user:rekono
password:rekono

This don't work!

Linux Mint latest.

[pablosnt]

This credentials should work in Docker environment. However, there were more issues like that, so I will review and try to reproduce this problem. Can you tell me if the directory where you clone Rekono is a non-root directory? The issue #33 has been resolved retrying from a non-root directory after remove all Docker images and volumes.

[zinwelzl]

Linux Mint latest, updated, in VirtualBox.
Non-root directory and non-root user.
What should I do?
Delete all images and volumes, and install again?

[zinwelzl]

images and volumes removed

docker-compose up -d
[+] Running 0/12
⠿ initialize Error 2.1s
⠿ frontend Error 2.1s
⠿ telegram-bot Error 2.1s
⠿ findings-worker Error 2.1s
⠿ postfix Error 2.1s
⠿ backend Error 2.1s
⠿ postgres Error 2.1s
⠿ redis Error 2.1s
⠿ emails-worker Error 2.1s
⠿ tasks-worker Error 2.1s
⠿ executions-worker Error 2.1s
⠿ nginx Error 2.1s
Error response from daemon: pull access denied for rekono-backend, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

[pablosnt]

I think that you didn't run docker-compose build first. I will review the problem carefully in your platform. By the time, please retry. As I said, it should works

[zinwelzl]

I did run build first, but still can't login.

[pablosnt]

Sorry, I have tried to reproduce the error in Linux Mint and I can't do it. Please, tell me if I'm doing something wrong:

OS information in VirtualBox:

After execute docker-compose build and docker-compose up -d:

Finally, I log in with default credentials rekono:rekono in the UI:

[pablosnt]

I advise to check the following items to prevent or get more information about the error:

• Check if the default user has been created in the initialize log.
• Check the API response using the browser development options: if the request arrives the backend and if credentials are wrong, the response should be 401.
• Check if the authentication requests arrives the Rekono API in the backend log.
• If requests don't arrive the backend, please reboot the nginx container because it doesn't forward the requests correctly.

Please, check this to know more about the error, and maybe fix it. And if you need, provide me this information to been able to help you.

[zinwelzl]

Nginx container was problem, after restart login work now!

Thanks for your help, great tool you build!

[zinwelzl]

BTW, just to let you know.

I did try few more Mint VM and every time same problem, and same solution with Nginx restart.

But with Kali, Rekono works great with first install and also in my cloud server.

[pablosnt]

Hello, after a more deep investigation, I was able to reproduce the error in Ubuntu and I think that the reason of the error could be the docker-compose version. In my local machine I have the following one and the dependencies between the containers are respected:

Otherwise, the error appears when I execute Rekono in Ubuntu with docker-compose 1.29.2 (https://github.com/pablosnt/rekono/actions/runs/3088518948/jobs/4995087093#step:3:4210). In the docker-compose logs you can check that the backend container is created before the database. So please, check your docker-compose version and upgrade it if needed. Let me know your conclusions, thank you!

[zinwelzl]

docker-compose version 1.29.2, build unknown

Same here, after upgrade rekono works!

[pablosnt]

Perfect!!! Thank you for keep trying. Your feedback about Linux Mint will be very useful to investigate future issues.

[pablosnt]

At the moment, the conclusions of this problem are:

• Upgrade your docker-compose --version. It has been tested that the Docker environment fails with versions like 1.29.2
• Check if the requests reach the backend container using the docker-compose logs. If not, reboot your nginx container to prevent forwarding errors
• Ensure that the default user has been created correctly in the initialize container using the docker-compose logs