On Linux the hub logs to standard output: with the provided unit, read it with journalctl -u doorhub. On Windows, as a service, it writes doorhub.log in the hub folder.

2026/11/09 11:30:36 Kalgoorlie Door Hub 0.1.0 listening on :2022 (key SHA256:dJxk...)
2026/11/09 11:32:39 BBS KAL connected from 10.0.0.46:51800
2026/11/09 11:32:41 New player [KAL]Heisenberg -> "Heisenberg (KAL)"
2026/11/09 11:32:42 [KAL]Heisenberg started lord
2026/11/09 11:45:22 [KAL]Heisenberg left lord after 12m40s
2026/11/09 11:50:03 Login refused for "kal_bbs" from 198.51.100.7:40122
2026/11/09 11:51:10 [KAL] refused [KAL]Bob: BBS disabled or removed
2026/11/09 11:52:00 Refused [KAL]Alice: password does not match

doorhub door list shows total plays per game and doorhub player list plays per player. The counts are in players.json (the plays field of each player) if you want to make your own lists, for example a bulletin of the most-played games.

Back up:

• the hub folder: hub.json, players.json, host_ed25519;
• your Synchronet user base (data/user) and the game folders, as you would anyway.

1. Stop the hub.
2. Copy the hub folder and the Synchronet BBS (or at least the games and user base) to the new machine.
3. Start the hub there, and point your DNS name at the new machine.

Because the host key moves with the folder, members don't need to change anything. A Linux hub folder works on Windows and the other way round; only the jsexec and sbbs_ctrl settings need changing.