[Bug] Unable to access romm system (500: Internal Server Error & 403: User not found)

[NicksGhost]

RomM version 3.3.0

Describe the bug After the deployment is completed using docker-compose, accessing the romm homepage console shows GET http://192.168.3.2:7990/api/heartbeat 500 (Internal Server Error); in the docker log it is fastapi.exceptions.HTTPException: 403: User not found, and it is also impossible to log in to the romm system.

version: '3.3'

services:
  romm_server:
    container_name: romm_server
    image: rommapp/romm:latest
    restart: unless-stopped
    depends_on:
      - romm_database
    ports:
      - 7990:8080
    environment:
      - DB_HOST=romm_database
      - DB_NAME=romm
      - DB_USER=romm-user
      - DB_PASSWD=[xxxxxxxx]
      - ROMM_AUTH_SECRET_KEY=[xxxxxxxx]
      - MOBYGAMES_API_KEY=[xxxxxxxx]
      - STEAMGRIDDB_API_KEY=[xxxxxxxx]
    volumes:
      - /volume1/docker/romm/assets:/romm/assets
      - /volume1/docker/romm/config:/romm/config
      - /volume1/docker/romm/library:/romm/library
      - /volume1/docker/romm/resources:/romm/resources
      - /volume1/docker/romm/data/redis:/redis-data

  romm_database:
    container_name: romm_database
    image: linuxserver/mariadb:latest
    restart: unless-stopped
    environment:
      - MYSQL_ROOT_PASSWORD=[xxxxxxxx]
      - MYSQL_DATABASE=romm
      - MYSQL_USER=romm-user
      - MYSQL_PASSWORD=[xxxxxxxx]
    volumes:
      - /volume1/docker/romm/data/mariadb:/var/lib/mysql

To Reproduce Steps to reproduce the behavior:

1. Run docker-compose.yml
2. Container service loading completed
3. Open romm's web ui
4. See error

Screenshots

• Docker console log:

• Browser console log:

Server

• OS: Synology DSM
• Version: 6.2.2

Desktop

• OS: Windwos 11
• Browser: Microsoft Edge
• Version: 23H2

[gantoine]

Are you logged in to any other apps on 192.168.3.2? The sessionid cookie might be colliding with one set by another app and stopping you from logging in. There's a fix already merged for this in master which will be in the next release.

[NicksGhost]

Are you logged in to any other apps on 192.168.3.2? The sessionid cookie might be colliding with one set by another app and stopping you from logging in. There's a fix already merged for this in master which will be in the next release.

Hi, thank you for your reply. Regarding the cookie problem you mentioned, I have tried clearing the browser cache, but it doesn’t seem to work. So the solution now is to wait for the next version update and try again?

[gantoine]

Yes that's possible, though I can't guarantee it'll fix it. We'll have a patch release out in a couple days.