[Bug]: Umami docker fails, login first fail

[akawahuynh]

Describe the Bug

I tried v2.14.0 still got the same error

My OS:
cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

uname -m
x86_64

Database

PostgreSQL

Relevant log output

2024-12-22T22:23:49.547322092Z yarn run v1.22.22
2024-12-22T22:23:49.595681812Z $ npm-run-all check-db update-tracker start-server
2024-12-22T22:23:50.158680325Z $ node scripts/check-db.js
2024-12-22T22:23:50.293932651Z ✓ DATABASE_URL is defined.
2024-12-22T22:23:50.375299791Z ✓ Database connection successful.
2024-12-22T22:23:50.431822014Z ✓ Database version check successful.
2024-12-22T22:23:51.590460405Z Prisma schema loaded from prisma/schema.prisma
2024-12-22T22:23:51.590494615Z Datasource "db": PostgreSQL database "umami", schema "public" at "postgresql:5432"
2024-12-22T22:23:51.590497695Z 
2024-12-22T22:23:51.590499786Z 7 migrations found in prisma/migrations
2024-12-22T22:23:51.590501846Z 
2024-12-22T22:23:51.590503686Z Applying migration `01_init`
2024-12-22T22:23:51.590505596Z Applying migration `02_report_schema_session_data`
2024-12-22T22:23:51.590507896Z Applying migration `03_metric_performance_index`
2024-12-22T22:23:51.590509915Z Applying migration `04_team_redesign`
2024-12-22T22:23:51.590511815Z Applying migration `05_add_visit_id`
2024-12-22T22:23:51.590513686Z Applying migration `06_session_data`
2024-12-22T22:23:51.590515556Z Applying migration `07_add_tag`
2024-12-22T22:23:51.590517466Z 
2024-12-22T22:23:51.590519316Z The following migration(s) have been applied:
2024-12-22T22:23:51.590521206Z 
2024-12-22T22:23:51.590523066Z migrations/
2024-12-22T22:23:51.590524966Z   └─ 01_init/
2024-12-22T22:23:51.590527766Z     └─ migration.sql
2024-12-22T22:23:51.590529726Z   └─ 02_report_schema_session_data/
2024-12-22T22:23:51.590531656Z     └─ migration.sql
2024-12-22T22:23:51.590533546Z   └─ 03_metric_performance_index/
2024-12-22T22:23:51.590535416Z     └─ migration.sql
2024-12-22T22:23:51.590537276Z   └─ 04_team_redesign/
2024-12-22T22:23:51.590539186Z     └─ migration.sql
2024-12-22T22:23:51.590541036Z   └─ 05_add_visit_id/
2024-12-22T22:23:51.590542896Z     └─ migration.sql
2024-12-22T22:23:51.590544716Z   └─ 06_session_data/
2024-12-22T22:23:51.590546556Z     └─ migration.sql
2024-12-22T22:23:51.590548376Z   └─ 07_add_tag/
2024-12-22T22:23:51.590550236Z     └─ migration.sql
2024-12-22T22:23:51.590552076Z       
2024-12-22T22:23:51.590554016Z All migrations have been successfully applied.
2024-12-22T22:23:51.590555916Z 
2024-12-22T22:23:51.590564257Z ✓ Database is up to date.
2024-12-22T22:23:51.859872513Z $ node scripts/update-tracker.js
2024-12-22T22:23:52.255480840Z $ node server.js
2024-12-22T22:23:52.595255720Z    ▲ Next.js 15.0.4
2024-12-22T22:23:52.595569723Z    - Local:        http://localhost:3000
2024-12-22T22:23:52.595614933Z    - Network:      http://0.0.0.0:3000
2024-12-22T22:23:52.595618703Z 
2024-12-22T22:23:52.595621224Z  ✓ Starting...
2024-12-22T22:23:52.691316439Z  ✓ Ready in 100ms
2024-12-22T22:24:58.260125220Z error Command failed with signal "SIGILL". 
2024-12-22T22:24:58.260238421Z info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 
2024-12-22T22:24:58.281960412Z ERROR: "start-server" exited with 1.
2024-12-22T22:24:58.297329682Z error Command failed with exit code 1.
2024-12-22T22:24:58.297435604Z info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2024-12-22T22:24:58.856589836Z yarn run v1.22.22
2024-12-22T22:24:58.895677758Z $ npm-run-all check-db update-tracker start-server
2024-12-22T22:24:59.311756973Z $ node scripts/check-db.js
2024-12-22T22:24:59.451708567Z ✓ DATABASE_URL is defined.
2024-12-22T22:24:59.529485924Z ✓ Database connection successful.
2024-12-22T22:24:59.586105816Z ✓ Database version check successful.
2024-12-22T22:25:00.648431503Z ┌─────────────────────────────────────────────────────────┐
2024-12-22T22:25:00.648482823Z │  Update available 5.17.0 -> 6.1.0                       │
2024-12-22T22:25:00.648489113Z │                                                         │
2024-12-22T22:25:00.648494213Z │  This is a major update - please follow the guide at    │
2024-12-22T22:25:00.648498843Z │  https://pris.ly/d/major-version-upgrade                │
2024-12-22T22:25:00.648503634Z │                                                         │
2024-12-22T22:25:00.648506963Z Prisma schema loaded from prisma/schema.prisma
2024-12-22T22:25:00.648508333Z │  Run the following to update                            │
2024-12-22T22:25:00.648513023Z │    yarn add --dev prisma@latest                         │
2024-12-22T22:25:00.648517603Z │    yarn add @prisma/client@latest                       │
2024-12-22T22:25:00.648522354Z └─────────────────────────────────────────────────────────┘
2024-12-22T22:25:00.648596314Z Datasource "db": PostgreSQL database "umami", schema "public" at "postgresql:5432"
2024-12-22T22:25:00.648604725Z 
2024-12-22T22:25:00.648609144Z 7 migrations found in prisma/migrations
2024-12-22T22:25:00.648613344Z 
2024-12-22T22:25:00.648617584Z 
2024-12-22T22:25:00.648621574Z No pending migrations to apply.
2024-12-22T22:25:00.648625765Z 
2024-12-22T22:25:00.648630164Z ✓ Database is up to date.
2024-12-22T22:25:00.963465050Z $ node scripts/update-tracker.js
2024-12-22T22:25:01.347011392Z $ node server.js
2024-12-22T22:25:01.959484010Z    ▲ Next.js 15.0.4
2024-12-22T22:25:01.960337498Z    - Local:        http://localhost:3000
2024-12-22T22:25:01.960356708Z    - Network:      http://0.0.0.0:3000
2024-12-22T22:25:01.960360239Z 
2024-12-22T22:25:01.960398179Z  ✓ Starting...
2024-12-22T22:25:02.122739468Z  ✓ Ready in 172ms

Which Umami version are you using? (if relevant)

v2.15.1

Which browser are you using? (if relevant)

Chrome 131.0.6778.205

How are you deploying your application? (if relevant)

Coolify

[mikecao]

You need to post the error that is in the box.

[akawahuynh]

yes the deploy process was fine, but it had problems during the first login

this log:

2024-12-24T07:15:13.677413054Z error Command failed with signal "SIGILL".
2024-12-24T07:15:13.677735705Z info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2024-12-24T07:15:13.702318229Z ERROR: "start-server" exited with 1.
2024-12-24T07:15:13.722795854Z error Command failed with exit code 1.
2024-12-24T07:15:13.723134876Z info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

and the server was restarted