msgbyte / msgbyte/tianji

Tianji Docker instance failing to start service

Open
#249 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.1k
Forks
194
Avg merge
18m
Merged PRs (30d)
3

Description

Tianji won't start

Been trying for days, with latest and other prior releases, with completely fresh instances, and severly failed to bring Tianji up and running.

I will miss Tianji for sure :(

Container log loop

> tianji@1.31.13 start:docker:db /app/tianji
> cd src/server && pnpm db:migrate:apply && pnpm ch:migrate:apply
2026/02/14 12:17:07 Send request error: Post "http://localhost:12345/serverStatus/report": dial tcp 127.0.0.1:12345: connect: connection refused
> @tianji/server@ db:migrate:apply /app/tianji/src/server
> prisma migrate deploy
2026/02/14 12:17:12 Send request error: Post "http://localhost:12345/serverStatus/report": dial tcp 127.0.0.1:12345: connect: connection refused
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "tianji", schema "public" at "tianji_postgres:5432"
2026/02/14 12:17:17 Send request error: Post "http://localhost:12345/serverStatus/report": dial tcp 127.0.0.1:12345: connect: connection refused
79 migrations found in prisma/migrations
No pending migrations to apply.
2026/02/14 12:17:22 Send request error: Post "http://localhost:12345/serverStatus/report": dial tcp 127.0.0.1:12345: connect: connection refused
> tianji@1.31.13 start:docker /app/tianji
> pnpm start:docker:db && pnpm start
> tianji@1.31.13 start:docker:db /app/tianji
> cd src/server && pnpm db:migrate:apply && pnpm ch:migrate:apply
> @tianji/server@ db:migrate:apply /app/tianji/src/server
> prisma migrate deploy
2026/02/14 12:17:35 Start reporting...
2026/02/14 12:17:35 Mode: http
2026/02/14 12:17:35 Version: 1.0.0
2026/02/14 12:17:40 Send request error: Post "http://localhost:12345/serverStatus/report": dial tcp 127.0.0.1:12345: connect: connection refused

Environment

  • Infrastructure: Linux LxC under Proxmox VE
  • Operating system: Alpine
  • Deployment: Docker
  • Reverse proxy: NginX Proxy Manager on anoterh LxC with SSL enabled

Docker compose

  tianji-redis:
    image: redis:latest
    restart: unless-stopped
    volumes:
      - ./Tianji/Redis/Data:/data
      - ./Tianji/Redis/Configuration:/usr/local/etc/redis

  tianji_postgres:
    image: postgres:15.4-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: tianji
      POSTGRES_USER: tianji
      POSTGRES_PASSWORD: tianji
    volumes:
      - ./Tianji/Postgres:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}"]
      interval: 5s
      timeout: 5s
      retries: 5

  tianji:
    image: moonrailgun/tianji:latest
    restart: unless-stopped
    tmpfs:
      - /tmp
    depends_on:
      - tianji-redis
      - tianji_postgres
    environment:
      PUBLIC_URL: ""
      ALLOW_REGISTER: false
      EMAIL_SERVER: "** REDACTED **"
      EMAIL_FROM: "** REDACTED **"
      JWT_SECRET: "** REDACTED **"
      CUSTOM_TRACKER_SCRIPT_NAME: "tianji.js"
      AMAP_TOKEN: "** REDACTED **"
      MAPBOX_TOKEN: "** REDACTED **"
      AUTH_CUSTOM_TYPE: "oidc"
      AUTH_CUSTOM_NAME: "** REDACTED **"
      AUTH_CUSTOM_ISSUER: "** REDACTED **"
      AUTH_CUSTOM_ID: "** REDACTED **"
      AUTH_CUSTOM_SECRET: "** REDACTED **"
      AUTH_GITHUB_ID: ""
      AUTH_GITHUB_SECRET: ""
      AUTH_GOOGLE_ID: ""
      AUTH_GOOGLE_SECRET: ""
      DISABLE_AUTO_CLEAR: false
      DISABLE_ANONYMOUS_TELEMETRY: true
      ALLOW_OPENAPI: true
      ENABLE_FUNCTION_WORKER: true
      DATABASE_URL: postgresql://tianji:tianji@tianji_postgres:5432/tianji
      REDIS_URL: redis://tianji-redis:6379
    ports:
      - 0.0.0.0:12345:12345

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with the provided Docker configuration and inspect the start:docker and start:docker:db entry points. Read prisma/schema.prisma and prisma/migrations alongside the container logs, especially the repeated serverStatus/report connection errors. Done means a fresh Docker instance completes startup and remains running without the reported loop.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, postgresql, typescript
Domain
databases, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.