New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't open N8N selfHosted #9148
Comments
Hey @igortsev, Do you see any errors in the docker logs? |
N8N_LOG_LEVEL:= 'info,warn,error,verbose,debug' - all clear, docker logs clear too. Just working after container restart. Tested that issue with 1.36.X with Docker compose Linux (Ubuntu22)/Windows 11. Just run and leave it ti 20 minutes and you wiil not open dashboard. Tested with localhost and VPS with HOST |
services:
traefik:
image: "traefik"
restart: always
command:
- "--api=true"
- "--api.insecure=true"
- "--providers.docker=true"
- "--providers.docker.exposedbydefault=false"
- "--entrypoints.web.address=:80"
- "--entrypoints.web.http.redirections.entryPoint.to=websecure"
- "--entrypoints.web.http.redirections.entrypoint.scheme=https"
- "--entrypoints.websecure.address=:443"
- "--certificatesresolvers.mytlschallenge.acme.tlschallenge=true"
- "--certificatesresolvers.mytlschallenge.acme.email=${SSL_EMAIL}"
- "--certificatesresolvers.mytlschallenge.acme.storage=/letsencrypt/acme.json"
ports:
- "80:80"
- "443:443"
volumes:
- traefik_data:/letsencrypt
- /var/run/docker.sock:/var/run/docker.sock:ro
n8n:
image: docker.n8n.io/n8nio/n8n
restart: always
ports:
- "127.0.0.1:5678:5678"
labels:
- traefik.enable=true
- traefik.http.routers.n8n.rule=Host(`${SUBDOMAIN}.${DOMAIN_NAME}`)
- traefik.http.routers.n8n.tls=true
- traefik.http.routers.n8n.entrypoints=web,websecure
- traefik.http.routers.n8n.tls.certresolver=mytlschallenge
- traefik.http.middlewares.n8n.headers.SSLRedirect=true
- traefik.http.middlewares.n8n.headers.STSSeconds=315360000
- traefik.http.middlewares.n8n.headers.browserXSSFilter=true
- traefik.http.middlewares.n8n.headers.contentTypeNosniff=true
- traefik.http.middlewares.n8n.headers.forceSTSHeader=true
- traefik.http.middlewares.n8n.headers.SSLHost=${DOMAIN_NAME}
- traefik.http.middlewares.n8n.headers.STSIncludeSubdomains=true
- traefik.http.middlewares.n8n.headers.STSPreload=true
- traefik.http.routers.n8n.middlewares=n8n@docker
environment:
- N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
- N8N_PORT=5678
- N8N_PROTOCOL=https
- NODE_ENV=production
- WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
- GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
- DB_TYPE=postgresdb
- DB_POSTGRESDB_HOST=postgres
- DB_POSTGRESDB_PORT=${POSTGRES_PORT}
- DB_POSTGRESDB_DATABASE=${POSTGRES_DB}
- DB_POSTGRESDB_USER=${POSTGRES_USER}
- DB_POSTGRESDB_PASSWORD=${POSTGRES_PASSWORD}
- N8N_LOG_LEVEL:= 'info,warn,error,verbose,debug'
links:
- postgres
volumes:
- n8n_data:/home/node/.n8n
postgres:
image: postgres:latest
restart: unless-stopped
environment:
POSTGRES_DB: ${POSTGRES_DB}
POSTGRES_USER: ${POSTGRES_USER}
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
ports:
- "5432:5432"
volumes:
- postgres_data:/var/lib/postgresql/data
volumes:
traefik_data:
external: true
n8n_data:
external: true
postgres_data:
external: true |
Hey @igortsev, I am not able to reproduce this, What I did was...
I then ran Gave it a few seconds then I loaded the page in my browser and completed the setup like normal. As this appears to be working fine I suspect there was an issue on your first run maybe with the database or traefik validating the email address for the SSL cert. Are you able to provide detailed steps on how to reproduce the issue? |
Moving to closed for now until we have a way to reproduce. |
Bug Description
Im installed N8N via Docker Compose from your config and N8N not accessebe after 20 min delay. I can open just after restart Docker containers. I tested on 2 different machines (Docker Linux and Windows) and have the same issue with Docker. Tested with SQLlite and PostgreSql, with Traefik and without
To Reproduce
Expected behavior
SignIn form or dashboard
Operating System
Ubuntu 22.04
n8n Version
1.36.4
Node.js Version
last
Database
PostgreSQL
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: