Fresh deployment - Unable to sign up

[kfoxton]

Hi all,

Attempting to spin this up in a VM. Deployed a new Rocky Linux 9 image, up to date. Installed Docker, then did the:

curl -LO https://raw.githubusercontent.com/prowler-cloud/prowler/refs/heads/master/docker-compose.yml
curl -LO https://raw.githubusercontent.com/prowler-cloud/prowler/refs/heads/master/.env
docker compose up -d

Dockers are pulled and start up, I can browse to the ip:3000 in my browser on the same network, but when I go to signup, I get an error in the web UI:

I look at the docker compose logs, and the only issue that I see in all the logs is in postgres:

2025-10-30 16:21:16.266 UTC [201] ERROR:  relation "django_celery_beat_crontabschedule" does not exist at character 321
2025-10-30 16:21:16.266 UTC [201] STATEMENT:  SELECT DISTINCT "django_celery_beat_crontabschedule"."timezone", "django_celery_beat_crontabschedule"."month_of_year", "django_celery_beat_crontabschedule"."day_of_month", "django_celery_beat_crontabschedule"."day_of_week", "django_celery_beat_crontabschedule"."hour", "django_celery_beat_crontabschedule"."minute" FROM "django_celery_beat_crontabschedule" ORDER BY "django_celery_beat_crontabschedule"."month_of_year" ASC, "django_celery_beat_crontabschedule"."day_of_month" ASC, "django_celery_beat_crontabschedule"."day_of_week" ASC, "django_celery_beat_crontabschedule"."hour" ASC, "django_celery_beat_crontabschedule"."minute" ASC, "django_celery_beat_crontabschedule"."timezone" ASC
2025-10-30 16:24:36.742 UTC [64] LOG:  checkpoint starting: time
2025-10-30 16:25:45.308 UTC [64] LOG:  checkpoint complete: wrote 679 buffers (4.1%); 1 WAL file(s) added, 0 removed, 0 recycled; write=67.686 s, sync=0.266 s, total=68.566 s; sync files=747, longest=0.049 s, average=0.001 s; distance=5111 kB, estimate=5111 kB; lsn=0/1E18970, redo lsn=0/1E18938

Is there something else I am missing to get this to work?

Thanks

[HugoPBrito]

Hello @kfoxton,

The problem seems to be that the files are downloaded from master, and it now has v5.13 files, so the .env file won't match the stable version of the docker image v5.12.3.

To fix this you need to get .env from the release version branch you want to use.

[kfoxton]

@HugoPBrito That seems to be it. Is there a way to get the docker files updated, so they are in line with the deployment docs?

[HugoPBrito]

Hi again @kfoxton,

Yes, it is. In fact, we worked on it and pushed a PR to fix this.

The current documentation should now show the correct commands that prevent the error you reported.
You can see it in https://docs.prowler.com/getting-started/installation/prowler-app.

[kfoxton]

Seems like the new steps are still not working with the versions that are being pulled from docker stable. Had to define in .env the 5.12.3 verson and repull to get it working when doing a fresh install again.

[HugoPBrito]

Seems like the new steps are still not working with the versions that are being pulled from docker stable. Had to define in .env the 5.12.3 verson and repull to get it working when doing a fresh install again.

Thanks for letting us know! I'll ping this as answer.