Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Token not working correctly with docker-compose #175

Closed
SOIT-SF opened this issue Jul 22, 2019 · 3 comments
Closed

Token not working correctly with docker-compose #175

SOIT-SF opened this issue Jul 22, 2019 · 3 comments
Assignees
Labels
confirmed-bug Issues with confirmed bugs

Comments

@SOIT-SF
Copy link

SOIT-SF commented Jul 22, 2019

I'm trying to get the token feature working in the docker-compose file.

I was expecting to be able to turn the feature on and pass a password to the pram
JWT_SECRET
This doesn't seem to work or I'm doing something wrong.
I've been testing with the connection to Nextcloud. When Nextcloud asks for url and secret I put what I've created into the fields, but get back an error that it's unable to connect. But if I leave the secret blank then it's able to connect.
I'm running this on a ubuntu 18.04 machine here is the configuration file I'm running for testing.

version: '2'
services:
  onlyoffice-documentserver-data:
    container_name: onlyoffice-documentserver-data
    image: onlyoffice/documentserver:latest
    environment:
      - ONLYOFFICE_DATA_CONTAINER=true
      - POSTGRESQL_SERVER_HOST=onlyoffice-postgresql
      - POSTGRESQL_SERVER_PORT=5432
      - POSTGRESQL_SERVER_DB_NAME=onlyoffice  
      - POSTGRESQL_SERVER_USER=onlyoffice
      - AMQP_SERVER_URL=amqp://guest:guest@onlyoffice-rabbitmq
      - REDIS_SERVER_HOST=onlyoffice-redis
      - REDIS_SERVER_PORT=6379
    stdin_open: true
    restart: always
    networks:
      - onlyoffice
    volumes:
       - /etc/onlyoffice
       - /var/www/onlyoffice/Data
       - /var/log/onlyoffice
       - /var/lib/onlyoffice/documentserver/App_Data/cache/files
       - /var/www/onlyoffice/documentserver-example/public/files
       - /usr/share/fonts
       
  onlyoffice-documentserver:
    image: onlyoffice/documentserver:latest
    depends_on:
      - onlyoffice-documentserver-data
      - onlyoffice-postgresql
      - onlyoffice-redis
      - onlyoffice-rabbitmq
    environment:
      - ONLYOFFICE_DATA_CONTAINER_HOST=onlyoffice-documentserver-data
      - BALANCE=uri depth 3
      - EXCLUDE_PORTS=443
      - HTTP_CHECK=GET /healthcheck
      - EXTRA_SETTINGS=http-check expect string true
      # Uncomment the string below to redirect HTTP request to HTTPS request.
      - FORCE_SSL=true
      - JWT_ENABLED=true
      - JWT_SECRET=<a password>
    stdin_open: true
    restart: always
    networks:
      - onlyoffice
    expose:
      - '80'
    volumes_from:
     - onlyoffice-documentserver-data

  onlyoffice-haproxy:
    container_name: onlyoffice-haproxy
    image: dockercloud/haproxy:1.5.1
    depends_on:
      - onlyoffice-documentserver
    environment:
      - MODE=http
      # Uncomment the string below to specify the path of ssl certificates
      - CERT_FOLDER=/certs/
    stdin_open: true
    links:
     - onlyoffice-documentserver
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      # Uncomment the string below to map a ssl certificate from host
      # to the proxy container
      #- /app/onlyoffice/DocumentServer/data/certs/onlyoffice.pem:/certs/cert1.pem
      - /data/onlyoffice/certs/onlyoffice.pem:/certs/cert1.pem
    restart: always
    networks:
     - onlyoffice
    ports:
      - '80:80'
      - '443:443'
      - '1936:1936'
       
  onlyoffice-redis:
    container_name: onlyoffice-redis
    image: redis
    restart: always
    networks:
     - onlyoffice
    expose:
      - '6379'

  onlyoffice-rabbitmq:
    container_name: onlyoffice-rabbitmq
    image: rabbitmq
    restart: always
    networks:
     - onlyoffice
    expose:
      - '5672'

  onlyoffice-postgresql:
    container_name: onlyoffice-postgresql
    image: postgres:9.5
    environment:
      - POSTGRES_DB=onlyoffice
      - POSTGRES_USER=onlyoffice
    networks:
      - onlyoffice
    restart: always
    expose:
      - '5432'
    volumes:
      - postgresql_data:/var/lib/postgresql

networks:
  onlyoffice:
    driver: 'bridge'

volumes:
  postgresql_data:
@SOIT-SF SOIT-SF changed the title Token Token not working correctly with docker-compose Jul 22, 2019
@ShockwaveNN
Copy link
Contributor

@downright77086 Hi, I agree. There is some kind of problem using JWT in Docker-Compose.
You can try to use it without docker compose, with Docker image, but we need time to figure out what to do with compose

@ShockwaveNN ShockwaveNN added the confirmed-bug Issues with confirmed bugs label Jul 23, 2019
@SOIT-SF
Copy link
Author

SOIT-SF commented Sep 12, 2019

Hi wondering if there is any update on this one

@agolybev
Copy link
Contributor

agolybev commented Sep 23, 2019

Hi @downright77086! You have to setup env variables JWT_ENABLED and JWT_SECRET to onlyoffice-documentserver-data container instead of onlyoffice-documentserver.

agolybev added a commit that referenced this issue Sep 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed-bug Issues with confirmed bugs
Projects
None yet
Development

No branches or pull requests

3 participants