go-vikunja / app

MIT License
250 stars 23 forks source link

issues with server-address and rw protection(?) #53

Closed cicci44 closed 8 months ago

cicci44 commented 8 months ago

using docker, when connection using laptop to frontend, everything works fine.. heres the config i used..

version: '3'

services:
  db:
    image: mariadb:10
    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
    environment:
      MYSQL_ROOT_PASSWORD: x
      MYSQL_USER: z
      MYSQL_PASSWORD: y
      MYSQL_DATABASE: y
    volumes:
      - ./srv/dev-disk-byx/appdata/vikunja/db:/var/lib/mysql
    restart: unless-stopped
  api:
    image: vikunja/api
    environment:
      VIKUNJA_DATABASE_HOST: db
      VIKUNJA_DATABASE_PASSWORD: x
      VIKUNJA_DATABASE_TYPE: mysql
      VIKUNJA_DATABASE_USER: y
      VIKUNJA_DATABASE_DATABASE: y
      VIKUNJA_SERVICE_JWTSECRET: x
      VIKUNJA_SERVICE_FRONTENDURL: http://192.168.1.100/
    ports:
      - 3456:3456
    volumes:
      - ./srv/dev-disk-byx/appdata/vikunja/files:/app/vikunja/files
    depends_on:
      - db
    restart: unless-stopped
  frontend:
    image: vikunja/frontend
    ports:
      - 8013:80
    environment:
      VIKUNJA_API_URL: http://192.168.1.100:3456/api/v1
    restart: unless-stopped

in android app..first time login.. with username/password at server address 192.168.1.100 gives error "no host specified" and the url looks like the http(s) is missing, changing it to http://192.168.1.100 gives error "error on request: failed host", i guess i need to specify port 8013 but it wont work either.. maybe port 3456? http://192.168.1.100:3456 gives "message": "not found", perhaps /api/v1 ? http://192.168.1.100:3456/api/v1 OK, now it works! .. suggestion is to add that as example like the try.vikunja.io address.

uhm, perhaps read/write error?

kolaente commented 8 months ago

Which vikunja version are you using?

cicci44 commented 8 months ago

Which vikunja version are you using?

Frontend Version: 0.21.0 API Version: v0.21.0 APK version 0.1.3-beta

kolaente commented 8 months ago

The last app release assumes a 0.22 api version.

Please note this is almost always the case, if not stated otherwise since it's still in beta.