in standalone CE, sign up& sign in are not working.

[plagdoctor]

I started teable project standalone CE in on-premise server(which is located vm server).

my docker-compose.yaml file in below.

version: '3.9'

services:
  teable:
    image: ghcr.io/teableio/teable:latest
    restart: always
    ports:
      - '3001:3000'
    volumes:
      - teable-data:/app/.assets:rw
    env_file:
      - .env
    environment:
      - NEXT_ENV_IMAGES_ALL_REMOTE=true
    networks:
      - teable
    depends_on:
      teable-db-migrate:
        condition: service_completed_successfully
      teable-cache:
        condition: service_healthy
        #    healthcheck:
        # test: ['CMD', 'curl', '-f', 'http://my_vm_server:3001/health']
      # start_period: 5s
      # interval: 5s
      # timeout: 3s
      # retries: 3

  teable-db:
    image: postgres:15.4
    restart: always
    ports:
      - '42345:5432'
    volumes:
      - teable-db:/var/lib/postgresql/data:rw
    environment:
      - POSTGRES_DB=${POSTGRES_DB}
      - POSTGRES_USER=${POSTGRES_USER}
      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
    networks:
      - teable
    healthcheck:
      test: ['CMD-SHELL', "sh -c 'pg_isready -U ${POSTGRES_USER} -d ${POSTGRES_DB}'"]
      interval: 10s
      timeout: 3s
      retries: 3

  teable-db-migrate:
"docker-compose.yaml" 81L, 1886C                                                                                43,1          19%
    volumes:
      - teable-data:/app/.assets:rw
    env_file:
      - .env
    environment:
      - NEXT_ENV_IMAGES_ALL_REMOTE=true
    networks:
      - teable
    depends_on:
      teable-db-migrate:
        condition: service_completed_successfully
      teable-cache:
        condition: service_healthy
        #    healthcheck:
        # test: ['CMD', 'curl', '-f', 'http://my_vm_server:3001/health']
      # start_period: 5s
      # interval: 5s
      # timeout: 3s
      # retries: 3

  teable-db:
    image: postgres:15.4
    restart: always
    ports:
      - '42345:5432'
    volumes:
      - teable-db:/var/lib/postgresql/data:rw
    environment:
      - POSTGRES_DB=${POSTGRES_DB}
      - POSTGRES_USER=${POSTGRES_USER}
      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
    networks:
      - teable
    healthcheck:
      test: ['CMD-SHELL', "sh -c 'pg_isready -U ${POSTGRES_USER} -d ${POSTGRES_DB}'"]
      interval: 10s
      timeout: 3s
      retries: 3

  teable-db-migrate:
    image: ghcr.io/teableio/teable-db-migrate:latest
    environment:
      - PRISMA_DATABASE_URL=postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/${POSTGRES_DB}
    networks:
      - teable
    depends_on:
      teable-db:
        condition: service_healthy

  teable-cache:
    image: redis:7.2.4
    restart: always
    expose:
      - '6379'
    volumes:
      - teable-cache:/data:rw
    networks:
      - teable
    command: redis-server --appendonly yes --requirepass ${REDIS_PASSWORD}
    healthcheck:
      test: ['CMD', 'redis-cli', '--raw', 'incr', 'ping']
      interval: 10s
      timeout: 3s
      retries: 3

networks:
  teable:
    name: teable-network

volumes:
  teable-db: {}
  teable-data: {}
  teable-cache: {}

I changed 2 things that Database HOST_NAME and teable inbound port 3000 to 3001.

my server is already using 3000 port and my docker container's name got difference name.

the docker container services is finely started with redis and postgresql, but sign in and sign up are not working.

the teable container logs are below,

# tried sign up but no response in chrome
{"level":50,"time":1736383376443,"pid":7,"hostname":"c0bc672efbfd","name":"teable","req":{"id":"f840bc4e32e75d1b742ed77d586f803d","method":"GET","url":"/api/auth/user/me","query":{},"params":{"0":"api/auth/user/me"},"remoteAddress":"::ffff:127.0.0.1","remotePort":55390},"context":"AuthGuard","spanId":"e1a2f04d96d588b4","traceId":"f840bc4e32e75d1b742ed77d586f803d","msg":"Auth session cookie is not found in request cookies"}
{"level":30,"time":1736383376446,"pid":7,"hostname":"c0bc672efbfd","name":"teable","req":{"id":"f840bc4e32e75d1b742ed77d586f803d","method":"GET","url":"/api/auth/user/me","query":{},"params":{"0":"api/auth/user/me"},"remoteAddress":"::ffff:127.0.0.1","remotePort":55390},"res":{"statusCode":401},"responseTime":5,"spanId":"e1a2f04d96d588b4","traceId":"f840bc4e32e75d1b742ed77d586f803d","msg":"request completed"}
{"level":30,"time":1736383376570,"pid":7,"hostname":"c0bc672efbfd","name":"teable","req":{"id":"f840bc4e32e75d1b742ed77d586f803d","method":"GET","url":"/auth/signup?","query":{},"params":{"0":"auth/signup"},"remoteAddress":"::ffff:172.29.42.66","remotePort":56054},"res":{"statusCode":200},"responseTime":291,"spanId":"9873576d476f1991","traceId":"f840bc4e32e75d1b742ed77d586f803d","msg":"request completed"}
{"level":30,"time":1736383376698,"pid":7,"hostname":"c0bc672efbfd","name":"teable","req":{"id":"7b77ff3bee49bce339dba1596e758173","method":"GET","url":"/images/favicon/favicon-32x32.png","query":{},"params":{"0":"images/favicon/favicon-32x32.png"},"remoteAddress":"::ffff:172.29.42.66","remotePort":56054},"res":{"statusCode":304},"responseTime":6,"spanId":"024680c7e4ee7843","traceId":"7b77ff3bee49bce339dba1596e758173","msg":"request completed"}

1. Is this project needed to host as only https protocol?? cause I didn't get DNS yet. should I put dns for server in advance. I tried only http with fixed IP.
2. is Enabling email service mandatory? I tried gmail smtp and outlook account, I don't know that I put env variables correctly or not.

thank you for read my issue. I am pleased any advice or comments.

[kpodp0ra]

From the logs you provided, everything seems to be working (positive error code on sign up).
It would be incredibly helpful if you could provide a bit more detail about the exact behavior you're observing.

1. Are you getting specific error messages in browser?
2. Is the application not starting, or you see login forms, but they are not behaving as expected?
3. Can you share all logs from start to finish? (upload them to Gist or something like that)

Even better, if possible, a short video demonstrating the issue would make it much easier to guide you toward a solution.

Is this project needed to host as only https protocol??

I don't have enough knowledge to respond to this, but modern browsers have cookie restrictions on HTTP sites. Consider using https://letsencrypt.org/