New Install, constant Notifications in bottom right with 404

Support
1

Hi All!

Took a look at this project and it looks perfect for my needs. But now that I register and login, I find that I constantly get notifications in the bottom left of the screen.

image

There is a failed network request that occurs in the dev tools to /api/v1/notifications?page=1 endpoint.

To note, I did try the original mariadb container but I wanted to be sure it wasn’t just the container having issues and that there wasn’t any weird timezone issues happening. The commands don’t translate over so they’re commented out but it happens on both mariadb:10 and the linuxserver variant. (doing searching I found I can use sqlite which I might move to anyway since my userbase isn’t large enough to warrant a full database but I don’t think this is the issue now).

Hopefully someone can help!
Thanks

Frontend Version: 0.18.1
API Version: v0.15.0+78-ea5dd87b12

Below is my compose file.

---
version: "3.9"

networks:
  reverse-proxy:
    name: reverse-proxy
  vikunja:
    internal: true

services:

  vikunja-api:
    image: vikunja/api
    container_name: vikunja-api
    hostname: vikunja-api
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - VIKUNJA_DATABASE_HOST=vikunja-db
      - VIKUNJA_DATABASE_PASSWORD=testing
      - VIKUNJA_DATABASE_TYPE=mysql
      - VIKUNJA_DATABASE_USER=vikunja
      - VIKUNJA_DATABASE_DATABASE=vikunja
    volumes: 
      - ${CONFIG}/vikunja:/app/vikunja/files
    networks:
      - reverse-proxy
      - vikunja
    depends_on:
      - vikunja-db
    restart: unless-stopped
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.vikunja-api-secure.entrypoints=websecure"
      - "traefik.http.routers.vikunja-api-secure.rule=Host(`tasks.${DOMAIN}`) && PathPrefix(`/api/v1`, `/dav/`, `/.well-known/`)"
      - "traefik.http.routers.vikunja-api-secure.tls=true"
      - "traefik.http.routers.vikunja-api-secure.service=vikunja-api-secure"
      - "traefik.http.services.vikunja-api-secure.loadbalancer.server.port=3456"

  vikunja-frontend:
    image: vikunja/frontend
    container_name: vikunja-frontend
    hostname: vikunja-frontend
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.vikunja-frontend-secure.entrypoints=websecure"
      - "traefik.http.routers.vikunja-frontend-secure.rule=Host(`tasks.${DOMAIN}`)"
      - "traefik.http.routers.vikunja-frontend-secure.tls=true"
      - "traefik.http.routers.vikunja-frontend-secure.service=vikunja-frontend-secure"
      - "traefik.http.services.vikunja-frontend-secure.loadbalancer.server.port=80"
    networks:
      - reverse-proxy
      - vikunja
    restart: unless-stopped

  vikunja-db:
    image: lscr.io/linuxserver/mariadb
    container_name: vikunja-db
    hostname: vikunja-db
    networks:
      - vikunja
  #  command:
  #    - "--character-set-server=utf8mb4"
  #    - "--collation-server=utf8mb4_unicode_ci"
  #    - "--max-connections=1000"
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - MYSQL_ROOT_PASSWORD=testing
      - MYSQL_DATABASE=vikunja #optional
      - MYSQL_USER=vikunja #optional
      - MYSQL_PASSWORD=testing #optional
    volumes:
      - ${CONFIG}/vikunja/mariadb:/config
    restart: always
2

It looks like your using a pretty old api version while the frontend is up to date. Hence the frontend tries to call api endpoints that simply don’t exist in the version you’re using and returns 404s.

Both the api and frontend should use 0.18.x

Since you don’t have any version pinned, it should be enough to run

docker-compose pull && docker-compose down && docker-compose up -d

to update everything. (Run it in the folder where your compose file is located)

3

Ah that fixed it, must be a problem with my docker as i just downloaded it yesterday. Maybe a mirror issue or something!

Thanks!

1 Like