ProxiTok icon indicating copy to clipboard operation
ProxiTok copied to clipboard

docker-compose error:(SIGNATURE_CONNECTION_ERROR)

Open ZevaXu opened this issue 3 years ago • 1 comments

Hello, I deployed with docker-compose, the web application is success to access but when go in to a url like https://example.com/@xxx, got a err below:

There was an error processing your request!

HTTP Code: 500

API error code 20 (SIGNATURE_CONNECTION_ERROR)

and I try set the API_FORCE_LEGACY=1, it still now work.

this is my docker-compose.yml:

version: '3'

services:
  web:
    container_name: proxitok-web
    image: ghcr.io/pablouser1/proxitok:master
    ports:
      - 8083:80
    environment:
      - LATTE_CACHE=/cache
      - API_CACHE=redis
      - REDIS_HOST=proxitok-redis
      - REDIS_PORT=6379
      - API_SIGNER_URL=http://proxitok-signer:8080/signature
      - API_FORCE_LEGACY=1
    volumes:
      - proxitok-cache:/cache
    depends_on:
      - redis
      - signer
  redis:
    container_name: proxitok-redis
    image: redis:7-alpine
    command: redis-server --save 60 1 --loglevel warning
    restart: unless-stopped
  signer:
    container_name: proxitok-signer
    image: ghcr.io/pablouser1/signtok:master
volumes:
  proxitok-cache:

ZevaXu avatar Jun 13 '22 14:06 ZevaXu

hmmm... It looks like that the signing server is not responding to the requests made by the frontend. I'm not really sure why though, right now the official docker-compose works perfectly out of the box

Also, please note that Legacy mode is no longer supported, so you should remove the API_FORCE_LEGACY env variable.

pablouser1 avatar Jul 03 '22 16:07 pablouser1

I solved creating a network so that both services could see each other.

glats avatar Oct 21 '22 12:10 glats