Thelounge - Settings are lost on browser restart

LSIO Discussion Container Support
1

I’m using thelounge in a Docker container on my Synology nas. I always want to stay connected to an IRC chat, however every time when I close my internet browser everything is gone.
There are 7 other Linuxserver containers running on my NAS, never had any problem with them.

I did map docker/configs/thelounge to /config and I added the right TZ, PGID and PUID. Changing the default value’s in the config file already made my life a bit easier but I would like to have all IRC servers to be persistent.

Value’s that I changed in the config file outside of the container:

	defaults: {
		name: "Freenode",
		host: "chat.freenode.net",
		port: 6697,
		password: "",
		tls: true,
		rejectUnauthorized: true,
		nick: "thelounge%%",
		username: "thelounge",
		realname: "The Lounge User",
		join: "#thelounge",
	},

Thanks in advance!

2

To ensure your IRC servers remain persistent in The Lounge Docker container, follow these steps:

  1. Enable User Authentication:
  • Edit your config.js file (located in docker/configs/thelounge) and set:

javascript

Copy

public: false,This requires users to log in, ensuring their data is saved.
2. Create a User via CLI:

  • Execute inside the container:

bash

Copy

docker exec -it thelounge thelounge add Set a password when prompted. Replace <username> with your desired name.
3. Add Servers via Web UI:

  • Log in at http://your-nas-ip:9000 using the created credentials.
  • Add your IRC servers through the UI. These will now save to docker/configs/thelounge/users/<username>.json.
  1. Verify File Permissions:
  • Ensure the /config directory and contents are owned by the PUID and PGID specified. Run:

bash

Copy

chown -R : /path/to/docker/configs/thelounge
5. Optional: Preconfigure Servers Manually:

  • Edit the user’s JSON file (e.g., username.json) and add server entries under networks following the existing format.

Why This Works: The Lounge only persists data for authenticated users. By disabling guest access and creating a user, your servers are stored in the user’s JSON file within the mapped /config volume, surviving browser sessions and container restarts.