Wrong token time leads to JWT token rejection.

I have a huge problem setting up the whiteboard app so far.
The bigest problem was, that the created JWT token somehow got a issue time that was ahead one hour.

The system time was fine, date and date -u showed the right time. Still the issued token was issued in the future.

This also renders the app completely useles since no tools are available for non collaborative working.

I use a docker compose setup:

app:
    image: nextcloud
    restart: always
    ports:
      - 9999:80
    links:
      - db
    volumes:
      - ./data:/var/www/html
    environment:
      - MYSQL_PASSWORD=***
      - MYSQL_DATABASE=***
      - MYSQL_USER=nextcloud
      - MYSQL_HOST=db
      - NEXTCLOUD_TRUSTED_DOMAINS=***

  nextcloud-whiteboard-server:
    image: ghcr.io/nextcloud-releases/whiteboard:stable
    restart: always
    ports:
      - "3002:3002"
    depends_on:
      - app
    environment:
      - NEXTCLOUD_URL=***
      - JWT_SECRET_KEY=SOMESECRET
      - MAX_UPLOAD_FILE_SIZE=10485760
      - RECORDINGS_DIR=/tmp/whiteboard-recordings
      - HOST=0.0.0.0
    volumes:
      - ./whiteboard-recordings:/tmp/whiteboard-recordings

Versions:
Whiteboard (1.5.4)
Nextcloud Hub 25 Autumn (32.0.5)

No source file or test is named. Start by reproducing the one-hour JWT issue with the supplied Docker Compose configuration and the listed Whiteboard and Nextcloud versions, then trace token issuance and validation. Done means identifying the time discrepancy's component and confirming that newly issued tokens are accepted.