Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)T
Posts
4
Comments
49
Joined
3 yr. ago

  • I've also tried to run the docker compose file with not changes from the Zitadel documentation, https://zitadel.com/docs/self-hosting/deploy/compose

    This is what shows:

     
        
    [+] Running 3/3
     ✔ Network root_zitadel      Created                                                                                                         0.0s 
     ✘ Container root-db-1       Error                                                                                                          60.8s 
     ✔ Container root-zitadel-1  Created                                                                                                         0.0s 
    dependency failed to start: container root-db-1 is unhealthy
    
    
      

    docker ps -a then shows the root-zitadel-1 container created but not started, I can't get any logs to show on the root-db-1 container even though it shows as running.....

    I start the root-zitadel-1 container and restart the root-db-1 container and this is what I get in the logs:

     
        
    time="2025-07-24T13:41:45Z" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:70"
    time="2025-07-24T13:41:45Z" level=fatal msg="unable to initialize the database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:63" error="failed to connect to `user=postgres database=postgres`: 172.18.0.2:5432 (db): dial error: dial tcp 172.18.0.2:5432: connect: connection refused"
    time="2025-07-24T13:41:45Z" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:70"
    time="2025-07-24T13:41:45Z" level=fatal msg="unable to initialize the database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:63" error="failed to connect to `user=postgres database=postgres`: 172.18.0.2:5432 (db): dial error: dial tcp 172.18.0.2:5432: connect: connection refused"
    time="2025-07-24T13:41:46Z" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:70"
    time="2025-07-24T13:41:46Z" level=fatal msg="unable to initialize the database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:63" error="failed to connect to `user=postgres database=postgres`: 172.18.0.2:5432 (db): dial error: dial tcp 172.18.0.2:5432: connect: connection refused"
    time="2025-07-24T13:41:47Z" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:70"
    time="2025-07-24T13:41:47Z" level=fatal msg="unable to initialize the database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:63" error="failed to connect to `user=postgres database=postgres`: 172.18.0.2:5432 (db): dial error: dial tcp 172.18.0.2:5432: connect: connection refused"
    time="2025-07-24T13:41:48Z" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:70"
    time="2025-07-24T13:41:48Z" level=fatal msg="unable to initialize the database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:63" error="failed to connect to `user=postgres database=postgres`: 172.18.0.2:5432 (db): dial error: dial tcp 172.18.0.2:5432: connect: connection refused"
    
      
  • Here is the compose file I'm using:

     
        
    services:
      postgresql:
        image: postgres:16-alpine
        container_name: postgresql
        restart: unless-stopped
        networks:
          - authentik
        healthcheck:
          test: ["CMD-SHELL", "pg_isready -d authentik -U postgres"]
          start_period: 20s
          interval: 30s
          retries: 5
          timeout: 5s
        volumes:
          - ./database:/var/lib/postgresql/data
        ports:
          - 5432:5432
        environment:
          POSTGRES_PASSWORD: JKSHDFUHWEUEIORUhdsjhfglsdhuifghert
          POSTGRES_USER: postgres
          POSTGRES_DB: authentik
      redis:
        image: redis:alpine
        container_name: redis
        command: --save 60 1 --loglevel warning
        restart: unless-stopped
        healthcheck:
          test: ["CMD-SHELL", "redis-cli ping | grep PONG"]
          start_period: 20s
          interval: 30s
          retries: 5
          timeout: 3s
        volumes:
          - ./redis:/data
        networks:
          - authentik
      server:
        image: ghcr.io/goauthentik/server:2025.6.4
        container_name: authentik-server
        restart: unless-stopped
        command: server
        environment:
          AUTHENTIK_SECRET_KEY: 0rIgYE/fgWwkkhKXob6jQQ8M8Wp6tJzDc658GGb0C5r0QZOt
          AUTHENTIK_REDIS__HOST: redis
          AUTHENTIK_POSTGRESQL__HOST: postgresql
          AUTHENTIK_POSTGRESQL__USER: postgres
          AUTHENTIK_POSTGRESQL__NAME: authentik
          AUTHENTIK_POSTGRESQL__PASSWORD: JKSHDFUHWEUEIORUhdsjhfglsdhuifghert
        volumes:
          - ./media:/media
          - ./custom-templates:/templates
        ports:
          - 9000:9000
          - 9443:9443
        networks:
          - authentik
        depends_on:
          postgresql:
            condition: service_healthy
          redis:
            condition: service_healthy
      worker:
        image: ghcr.io/goauthentik/server:2025.6.4
        container_name: authentik-worker
        restart: unless-stopped
        command: worker
        networks:
          - authentik
        environment:
          AUTHENTIK_SECRET_KEY: 0rIgYE/fgWwkkhKXob6jQQ8M8Wp6tJzDc658GGb0C5r0QZOt
          AUTHENTIK_REDIS__HOST: redis
          AUTHENTIK_POSTGRESQL__HOST: postgresql
          AUTHENTIK_POSTGRESQL__USER: postgres
          AUTHENTIK_POSTGRESQL__NAME: authentik
          AUTHENTIK_POSTGRESQL__PASSWORD: JKSHDFUHWEUEIORUhdsjhfglsdhuifghert
        user: root
        volumes:
          - /var/run/docker.sock:/var/run/docker.sock
          - ./media:/media
          - ./certs:/certs
          - ./custom-templates:/templates
        depends_on:
          postgresql:
            condition: service_healthy
          redis:
            condition: service_healthy
    networks:
      authentik:
    
      
  • Here are the logs when starting up Authentik docker compose:

     
        
    authentik-worker  | {"event": "Starting authentik bootstrap", "level": "info", "logger": "authentik.lib.config", "timestamp": 1753364156.1238139}
    authentik-worker  | {"event": "PostgreSQL connection failed, retrying... (connection failed: connection to server at \"172.18.0.3\", port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?)", "level": "info", "logger": "authentik.lib.config", "timestamp": 1753364157.1261947}
    authentik-worker  | {"event": "PostgreSQL connection failed, retrying... (connection failed: connection to server at \"172.18.0.3\", port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?)", "level": "info", "logger": 
    authentik-server  | {"event":"Loaded config","level":"debug","path":"inbuilt-default","timestamp":"2025-07-24T13:35:48Z"}
    authentik-server  | {"event":"Loaded config","level":"debug","path":"/authentik/lib/default.yml","timestamp":"2025-07-24T13:35:48Z"}
    authentik-server  | {"event":"Loaded config from environment","level":"debug","timestamp":"2025-07-24T13:35:48Z"}
    authentik-server  | {"event":"Starting HTTP server","level":"info","listen":"0.0.0.0:9000","logger":"authentik.router","timestamp":"2025-07-24T13:35:49Z"}
    authentik-server  | {"event":"Starting Metrics server","level":"info","listen":"0.0.0.0:9300","logger":"authentik.router.metrics","timestamp":"2025-07-24T13:35:49Z"}
    authentik-server  | {"event":"Starting HTTPS server","level":"info","listen":"0.0.0.0:9443","logger":"authentik.router","timestamp":"2025-07-24T13:35:49Z"}
    authentik-server  | {"event": "Loaded config", "level": "debug", "logger": "authentik.lib.config", "timestamp": 1753364149.613906, "file": "/authentik/lib/default.yml"}
    authentik-server  | {"event": "Loaded environment variables", "level": "debug", "logger": "authentik.lib.config", "timestamp": 1753364149.6143358, "count": 6}
    authentik-server  | {"event": "Starting authentik bootstrap", "level": "info", "logger": "authentik.lib.config", "timestamp": 1753364149.953862}
    authentik-server  | {"event": "PostgreSQL connection failed, retrying... (connection failed: connection to server at \"172.18.0.3\", port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?)", "level": "info", "logger": "authentik.lib.config", "timestamp": 1753364150.955268}
    authentik-server  | {"event": "PostgreSQL connection failed, retrying... (connection failed: connection to server at \"172.18.0.3\", port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?)", "level": "info", "logger": 
    
      
  • time="2025-07-23T20:49:22Z" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:75" time="2025-07-23T20:49:22Z" level=fatal msg="unable to initialize the database" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:68" error="failed to connect to user=root database=postgres:\n\t127.0.0.1:5432 (localhost): dial error: dial tcp 127.0.0.1:5432: connect: connection refused\n\t[::1]:5432 (localhost): dial error: dial tcp [::1]:5432: connect: connection refused" time="2025-07-23T20:49:23Z" level=info msg="initialization started" caller="/home/runner/work/zitadel/zitadel/cmd/initialise/init.go:75"

    When I run docker compose up it's initializes all the containers and then the zdb container fails to load and I get the error messages above. I can't seem to paste my docker compose file or environment files since it formats the code very weirdly and makes it hard to read.

  • Yeah I'll grab some logs and post my files tonight when I get time :)

  • I definitely can't connect to the container as it doesn't start. I've also tried without the .env file and that doesn't work either. I've even setup a new LXC and started from scratch with the same result. For reference I'm using Ubuntu server so maybe I'll try a different distro..

  • Ah thanks for that info I'll definitely take a look

  • Can I ask how you have this setup? Do you also have a reverse proxy setup or just WG on your router and everything gets routed via your router?

  • I used wireguard self hosted for a bit but my work network is pretty locked down and I couldn't find a UDP port that wasn't blocked. How are you guys setting up wireguard in your home network? Or is it better to host it on a cloud VM?

    I'm using tailscale right now because it punches through every firewall but I don't like using external providers and I'm worried it will eventually enshittify. I have a cloudflare domain but I can't really use any UDP port for my VPN as it's blocked.

  • I blocked my printer from having internet access and blocking its random DNS attempts as well 2 months after I bought it. They are amazing printers for beginners and priced very well IMO. I love my printer bit will never update the firmware because of this enshittification.

  • I'm self hosting audiobookshelf with tailscale. Also use home assistant with music assistant to play my podcasts on all my home speakers as well.

  • I figured this out. My depth of the text was wrong and I was able tofiguree out how to embed the text into the project so we are good! I've tried orcaslicer but it won't open on my fedora setup for some reason and I'm also running Bambi studio in docker which is nice.

  • This the main reason I switched from traefik, I can have certificates on all my internal stuff and not just on my docker host. I personally love NPM but maybe I'll give NPMPlus a try, I have never heard of it.

  • Lan mode only, firewall blocking all internet access to it and I'm good to go. Bambu studio connects to it fine and still works with homeassistant as well.

  • Let me know if you find the 1.03 firmware version as I can't seem to find it anywhere on their site. The latest for the a1 mini is 1.04 and it was released on December 10th.

    If you find 1.03 please post it in here! :)

  • What's the latest firmware version that shittifies these printers? I have an a1 mini with version 1.4

  • Dang thanks for this, I have vlans and use opnsense but I couldn't figure out how to connect to the printer from bambu studio. Ive installed the udpbroadcastrelay plugin on opnsense but it still doesn't seem to connect. Do you mind posting a screenshot of your pfsense config?

    Thanks for posting this!

  • Yeah this sucks, I just bought an a1 mini with AMS, I love it. I do have it in LAN Mode with no internet and I still use bambustudio since I believe that is open source no? Lets hope they reverse this but I don't see them doing that. Hope I can still use the printer without upgrading the firmware or somebody is able to make open source firmware for the a1 mini...

    Man I hate tech space right now, every company grinding out as much money as possible anyway they can because "security"...

  • So I'm just not going to update mg firmware then? I'm already using lan only mkde, and if I have to start using an SD card I guess I can do that.

    My A1 mini is 3 weeks old and I love it but this sucks.... It always starts with "security" and i can totally see them going subscription model and locking you into their ecosystem. I guess that's why it was so cheap and on sale haha. Sucks to see such an amazing product and success to go downhill so quickly...

  • Dumb question but is there a way to automatically backup my compose files to my local gitea instance?