pablosnt / rekono

Pentesting automation platform that combines hacking tools to complete assessments
https://github.com/pablosnt/rekono/wiki
GNU General Public License v3.0
439 stars 67 forks source link

no login screen, Can't open "/etc/nginx/tls/privatekey.key" for writing, Permission denied #320

Closed zinwelzl closed 1 month ago

zinwelzl commented 1 month ago

docker compose install in parrotos

can not login, just white screen

this is output

nginx | req: Can't open "/etc/nginx/tls/privatekey.key" for writing, Permission denied backend | 2024-10-05 15:17:08,141 [INFO] - 31 middleware - 127.0.0.1 - anonymous - GET /api/schema/swagger-ui.html > HTTP 200 nginx exited with code 1 frontend | HTTP 10/5/2024 1:17:15 PM 127.0.0.1 GET / frontend | HTTP 10/5/2024 1:17:15 PM 127.0.0.1 Returned 200 in 110 ms backend | 2024-10-05 15:17:18,787 [INFO] - 31 middleware - 127.0.0.1 - anonymous - GET /api/schema/swagger-ui.html > HTTP 200 nginx | ++++++++++++++++++++++++++++++++++++++++++++*

pablosnt commented 1 month ago

Hi,

This is a common issue, so you can check the solution on the FAQ. Please, let me know if this works for you.

Anyway, I will explore alternatives to avoid situations like this in the next version.

Thank you for reporting the issue

zinwelzl commented 1 month ago

This works, thanks.

Permission error during Nginx execution The reason for the following Nginx failure is the lack of permissions from Docker execution over docker/nginx/tls/ directory:

nginx | req: Can't open "/etc/nginx/tls/privatekey.key" for writing, Permission denied It could happen when the Rekono repository is cloned using one system user and Docker is being executed with another system user. To solve the problem, it's needed to give read and write permissions over the directory docker/nginx/tls/ to the system user that is executing Docker. For example, the following command can be used to give read and write access to all system users:

chmod -R 666 docker/nginx/tls/