[BUG] Web-UI is accessible much later after starting the container compared to previous versions

[Liopleus]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

In 4.5.0-ls223, it takes a few minutes for webui to be accessible after "[ls.io-init] done." is shown in the docker terminal.
It's almost immediately accessible after starting the container in 4.4.x versions.

Expected Behavior

No response

Steps To Reproduce

In Docker Windows x64, spin up a container with "docker compose up -d". There's data carried from container on previous version and the volume is directly mapped to directories in NTFS partition.

Environment

- OS: Windows 11 x64
- How docker service was installed: winget

CPU architecture

x86-64

Docker creation

services:
  thelounge:
    image: lscr.io/linuxserver/thelounge:latest
    container_name: thelounge
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=${TZ}
    volumes:
      - ./:/config
    ports:
      - 9000:9000
    restart: unless-stopped

Container logs

[migrations] started

[migrations] no migrations found

usermod: no changes

───────────────────────────────────────


      ██╗     ███████╗██╗ ██████╗

      ██║     ██╔════╝██║██╔═══██╗

      ██║     ███████╗██║██║   ██║

      ██║     ╚════██║██║██║   ██║

      ███████╗███████║██║╚██████╔╝

      ╚══════╝╚══════╝╚═╝ ╚═════╝


   Brought to you by linuxserver.io

───────────────────────────────────────


To support LSIO projects visit:

https://www.linuxserver.io/donate/


───────────────────────────────────────

GID/UID

───────────────────────────────────────


User UID:    1000

User GID:    1000

───────────────────────────────────────

Linuxserver.io version: v4.5.0-ls223

Build-date: 2026-05-20T06:35:52+00:00

───────────────────────────────────────

    

[custom-init] No custom files found, skipping...

2026-05-22 06:07:54 [WARN] /config/logs is world readable. The log files may be exposed. Please fix the permissions.

2026-05-22 06:07:54 [WARN] run `chmod o-x "/config/logs"` to correct it.

2026-05-22 06:07:55 [INFO] The Lounge v4.5.0 (Node.js 22.22.2 on linux x64)

2026-05-22 06:07:55 [INFO] Configuration file: /config/config.js

(node:147) ExperimentalWarning: SQLite is an experimental feature and might change at any time

(Use `node --trace-warnings ...` to show where the warning was created)

2026-05-22 06:07:55 [INFO] Available at http://[::]:9000/ in private mode

2026-05-22 06:07:55 [WARN] /config/vapid.json is world readable. The file contains secrets. Please fix the permissions.

2026-05-22 06:07:55 [WARN] run `chmod o= "/config/vapid.json"` to correct it.

2026-05-22 06:07:55 [INFO] User XXX loaded

Connection to localhost (::1) 9000 port [tcp/*] succeeded!

[ls.io-init] done.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[Swag7User]

I can confirm this same behavior on unraid with lscr.io/linuxserver/thelounge:4.5.0
Downgrading to lscr.io/linuxserver/thelounge:4.4.3 fixed it.
It also lost connection after a while (~24h) which only restarting the container fixed.

[Liopleus]

I might have found a solution. Changing messageStorage in config.js from ["sqlite", "text"] to ["sqlite"] and delete the existing sqlite file solved the issue and greatly improves searching performance on top of that.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[aptalca]

Ntfs is likely the issue. Sqlite is very picky about file systems and does not work in remote mounts. While your ntfs mount is not necessarily remote, it still goes through an abstraction layer when mounted in docker.

We do not recommend ntfs mounts (or remote mounts) for the config folder in our containers. Wsl with a linux path for config is highly recommended.