Failed to validate signup details

[Fixer33]

After I start the service, I am trying to sign up and get: "Failed to validate signup details"

I have checked my db - it works and contains tables, backend is able to connect to it.

[kalinga777]

Hi @Fixer33 - could you elaborate more about this ?

[b0bb3s]

Signup fails with “failed to validate sign up details” on fresh Docker installation

Hello @kalinga777
I expirence the same issue. I performed a fresh installation of Worklenz using the official Docker setup from the repository:

👉 https://github.com/Worklenz/worklenz/blob/main/DOCKER_SETUP.md

All containers start successfully, the frontend loads, and the signup page is accessible.
However, creating a new user fails with the UI error message:

• "failed to validate sign up details"

No user is created in the database.

Reproductionsteps:

1. Fresh Debian/Ubuntu server
2. Clone repository
3. Run ./quick-setup.sh
4. Run docker compose up -d
5. Open /auth/signup
6. Fill out the form and submit
7. UI shows: “failed to validate sign up details”
8. No user is created

Should do:

• The first user should be created successfully and become the owner/admin.

Is doing:

1. UI shows: “failed to validate sign up details”
2. No backend error is shown
3. No user is inserted into the database
4. No seed data appears to be present (no teams, no roles, no permissions)

Backend Logs (anonymized):
[Backend] Storage provider initialized: s3
[Backend] Using endpoint: http://minio:9000
[Backend] Bucket: your-bucket-name
[Backend] Listening on port 3000
[Backend] DbTaskStatusChangeListener connected.
[Backend] GET /public/health 200

Systeminformationen:

• Worklenz version: latest (Docker Hub)
• Deployment method: official Docker setup (quick-setup.sh)
• OS: Debian 12 (fresh install)
• Docker Compose v2

Summary:
The installation completes without errors, but no seed data is created, and user registration fails with “failed to validate sign up details”.
It appears that the current Docker images do not execute any seed scripts, leaving the database empty and preventing signup.
Could you please confirm whether seed execution is missing in the current Docker images or whether an additional step is required?
Thank you!

[kalinga777]

@Fixer33 Thank you for the detailed report. Will check and update @chamikaJ

[RYUcze]

Same issue here, again clean install on fresh VM.
#EPICFAIL

[ekomsctr]

Same issue trying to setup a local instance on Docker. Moreover, when i run the quick-setup script, it stops at "Setting up self-signed SSL certificates for localhost..."

[binomnom]

@kalinga777 to add to this, I am pretty sure it's a URL port utilization bug.

.env contents:

Only relevant lines.

# ============================================================================
# DOMAIN AND URL CONFIGURATION
# ============================================================================
# Your domain name (e.g., worklenz.example.com)
# For localhost testing: localhost
# For production: your-domain.com
DOMAIN=localhost

# Base URL for the API (used by frontend to connect to backend)
# For production with HTTPS: https://your-domain.com
# For localhost HTTP: http://localhost
VITE_API_URL=https://localhost

# WebSocket URL for real-time features
# For production with HTTPS: wss://your-domain.com
# For localhost: ws://localhost
VITE_SOCKET_URL=wss://localhost

# Frontend URL (used by backend for CORS and redirects)
# Should match your domain URL
FRONTEND_URL=https://localhost

# CORS Configuration
# For development: * (allows all origins)
# For production: your-domain.com or https://your-domain.com
SERVER_CORS=*
SOCKET_IO_CORS=*

# ============================================================================
# PORT CONFIGURATION
# ============================================================================
# Ports exposed to the host machine
HTTP_PORT=1337
HTTPS_PORT=4444

Steps to reproduce:

1. Setup:

git clone https://github.com/Worklenz/worklenz.git
cd worklenz
cp .env.example .env
# edit .env file
docker compose --profile express up -d

2. Navigate to https://localhost:4444
3. Klick sign up

Reason why I believe it's a port issue:

Every time the Sign Up button is clicked, the following is logged in the browser console:

which is then blocked because of CORS, which is also weird, given that I have allowed all origins in the `.env`. But even if it wasn't, that's not where the backend is listening...

[aboualiaa]

I also had this while trying to install for production using my domain, I think somewhere in the frontend "localhost" is hard-coded, that's why it fails in the browser because it tries to send requests to "localhost" from a remote machine on the internet, will dig deeper into the issue when I have time, maybe try to build the docker images myself with correct env variables.

[Sadeqss]

I have the same issue. I installed it today. When I want to signup a new user so I can log in, it says "Failed to validate signup datailes".
Im not a tech person but it seems it failes to get a response for "csrf-token" request