msgbyte / msgbyte/tianji

Hetzner VPS is not visible in server tab (with Coolify)

Open
#147 2 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

Hi, as the title claims; my hetzner VPS is not visible in server tab even report show success.

I have installed Tianji through a docker compose on a Coolify instance. Here is an example of my docker compose file:

version: '3.8'
services:
  tianji:
    image: 'moonrailgun/tianji:latest'
    ports:
      - '12354:12345'
    environment:
      DATABASE_URL: 'postgresql://tianji:tianji@postgres:5432/tianji'
      JWT_SECRET: super_secret
      ALLOW_REGISTER: 'false'
      ALLOW_OPENAPI: 'true'
      OPENAI_API_KEY: super_secret
    depends_on:
      postgres:
        condition: service_healthy
    networks:
      - tianji_network
    restart: always
  postgres:
    image: 'postgres:15.4-alpine'
    environment:
      POSTGRES_DB: tianji
      POSTGRES_USER: tianji
      POSTGRES_PASSWORD: super_secret
    ports:
      - '5440:5432'
    volumes:
      - 'tianji-db-data:/var/lib/postgresql/data'
    networks:
      - tianji_network
    restart: always
    healthcheck:
      test:
        - CMD-SHELL
        - 'pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}'
      interval: 15s
      timeout: 5s
      retries: 5
volumes:
  tianji-db-data: null
networks:
  tianji_network:
    driver: bridge

I have read on the docs that it may be related to reverse proxy, however not sure if Coolify is using nginx internally. There is a way to configure Traefik/Caddy. Since Tianji is not available yet, I tried with a compose file, however I am not sure what I should include there for adding websocket to reverse proxy. Not really sure if that is the problem either.

image
Screenshot 2025-01-14 at 21 41 09

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 with the server tab behavior and the supplied Docker Compose configuration, then review how the Coolify deployment and its reverse proxy handle the server report and websocket connection. Confirm whether the VPS becomes visible through the documented deployment setup; the issue is done when the server report succeeds and the VPS appears in the server tab.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, postgresql
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.