Owner account creation fails

Describe the problem/error/question

Freshly installed PoC for n8n.

Compose file:

version: '3.8'

volumes:
  n8n_storage:

services:
  n8n:
    image: docker.n8n.io/n8nio/n8n
    env_file: env
    network_mode: host
    volumes:
      - ./n8n_storage:/home/node/.n8n:Z

Env file:

DB_TYPE=postgresdb
DB_POSTGRESDB_HOST=localhost
DB_POSTGRESDB_PORT=5432
DB_POSTGRESDB_DATABASE=n8n
DB_POSTGRESDB_USER=n8n
DB_POSTGRESDB_PASSWORD=n8n-test

GENERIC_TIMEZONE=Europe/Prague
N8N_LOG_LEVEL=debug
N8N_LOG_OUTPUT=console,file
N8N_HOST=XXX.XXX.XXX.23 # ipaddr of the host
N8N_PORT=5678
N8N_PROTOCOL=http

Volume works fine, files are created. Database connectivity is also fine, db objects are created.

Application seems to serve pages, when I browse the IP the initial Set up owner account page loads.

Data I fill into fields:
Email: [email protected]
First Name: John
Last Name: Doe
Password: Password123

I tried to create the account in Firefox and in Vivaldi, both fail.

What does one need to do to be able to create initial account?
Why is nothing logged for this 401 anywhere (even though the app runs in debug mode)?

What is the error message (if any)?

Problem setting up owner
Request failed with status code 401

Information on your n8n setup

  • n8n version: 1.31.2 (current latest tag)
  • Database (default: SQLite): PGSQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Podman container
  • Operating system: Doesn’t matter, it’s container.

It’s definitely bug in this version, I just tried to downgrade to 1.30.0 and I can set up the owner account just fine.

Thus the registration is some sort of bug, but the question about nothing being logged in still remains…

EDIT: The logging seems worthless so far, I just filled in the initial questionnaire and it says Error while submitting results Can’t connect to n8n. Nothing is logged again. Any plans on implementing actual working logs?

hello @petr.tuma

As you are not using the HTTPS, that workaround should help

1 Like

New version [email protected] got released which includes the GitHub PR 8906.