The docs tree is laid out like the menus - a menu path is a docs path. Admin Panel / Settings follows the new structure: Visibility.md is Appearance.md, with new Features.md, Feature-Profiles.md, Security.md, Activities-and-Notifications.md and Delete.md; the section indexes, Admin-Panel.md, Admin-Panel-URLs.md (with the moved-pane redirects) and Validation.md follow the live menus, and Who-Sees-What.md explains in one place which layer decides what is shown and what is allowed. Pages are added for the menu entries that had none, each written from the code: every Admin Panel / Problems pane, the member menu, the board header, Board Settings, the All Boards left menu, and the list, swimlane and card menus. Older links to the moved panes are updated across docs/. TODO.md records what documenting the menus found: Edit Profile does not save a username for non-admins, the Support page's signed-out case is unreachable, Create board from this card is hidden from members who can edit the card, All Boards Settings is unreachable, and the Share template targets live in browser storage. Thanks to xet7 !
Admin Panel → Problems
Status: Implemented · Owner: xet7
Admin Panel → Problems is where a WeKan admin sees what is wrong or in
progress: performance (CPU / RAM / disk), data-safety and recovery, migrations and
repairs, broken data, and the causes that can keep users off the login page. Open
it at Admin Panel → Problems (you must be an admin — currentUser.isAdmin).
The same information is available without the Admin Panel, from the server
command line, via snap run wekan.problems — see Snap.md — so an
admin who only has server (snap) access can read it without being given Admin
Panel access. It is also on the REST API, for monitoring from outside:
GET /api/admin/problems is this overview with the new-problem count per
stream, GET /api/admin/problems/:stream one page of a stream, and
POST /api/admin/problems/:stream/acknowledge the acknowledge button - see
REST API.
The Status overview (Problems → Summary)
The Summary pane (Summary.md) shows a Status overview at the top:
- In progress — every migration or repair running right now (database text migration, board data-repair, recovery/maintenance, attachment migration), gathered from the persisted status collections so it is accurate even across a restart.
- Problems — detected issues: broken cards, lists missing their swimlane, a failed or overdue backup, data health findings, and any failing login-page check — the known causes that make the login page show "Must be logged in" or sit on the logo + "Loading, please wait." spinner (see Login-Problems.md).
Below that are the data health scan and the acknowledge / clear list of the problem streams. What each stream records is on its own page: the Security Report also records denied passwordless code requests, the Meteor 3.5.3 refusals and import / export validation, see Security-Report.md.
The menu
Admin Panel / Problems opens on Summary, then Backup, then the Reports group.
Security, Delete and Notifications used to be a "Settings" group
here. They are settings, not problems, and on 2026-11-19 they moved to Admin
Panel / Settings as Security,
Delete and
Activities and notifications.
Their old /admin/problems/... addresses redirect there.
- Summary — what is running, what is wrong, and the new-problem count of each stream, with the repair, acknowledge and clear buttons.
- Backup — did the Admin Panel backup work: the last successful backup, the last failure and its error, the next scheduled run, and the history of the last runs. Its settings stay in Admin Panel / Attachments / Backup; a failed or overdue backup is also listed on Summary (Backup.md).
Reports — Security Report, Impersonation Report, Password length,
Performance, Speed, Tests, CPU usage, Memory Usage, Disk usage,
Instrumentation, Broken Cards, Files Report, Rules Report, Boards Report, Cards
Report, Recovery, Offices, API, Database problems, Filesystem integrity and
Email. Report tables use the shared table page: a
search box, the total, page X / N, prev/next, and one page of rows fetched
from the server at a time. Performance sits with the Speed / Tests / CPU
usage streams: card loading is automatic per board size, with
CARDS_LOADING=all|lazy|auto and CARDS_LOADING_LAZY_THRESHOLD for operators.
Detailed pages in this directory
| Page | What it covers |
|---|---|
| Repairs.md | Automatic board data-repairs (#6484 lists that vanish, orphaned/missing-swimlane cards): what they fix, when they run (board open, server startup, during migration), and the progress dashboard. |
| Data-Health.md | The nightly data health scan (#6818): read-only checks for data WeKan should never write (a card on a list of another board, checklist items of a deleted checklist, members whose account is gone), shown in Problems / Summary with a Repair button - one click for a repair that only moves data, a confirming second click, checked by the server, for one that deletes. |
| Migrations.md | The MongoDB ↔ FerretDB v1 (SQLite) text-data migration, the repair phase it runs, and the shared blue, Product-name-branded progress dashboard. |
| Login-Problems.md | Everything that can make the login page show "Must be logged in" or a stuck "Loading, please wait." spinner, and how to fix each. |
| Snap.md | The snap run wekan.problems commands that print this whole overview (and problem-specific detail like CPU) as text. |
| CPU-usage.md | CPU-usage monitor / governor and the CPU report. A pegged ferretdb process is the usual cause of slow pages. |
| RAM-usage.md | RAM-usage report. |
| Large-Boards.md | What a large board loads (lazy card windows, card details on open, streamed attachments), the #6745 measurements, and sizing for 8 GB of RAM. |
| Disk-usage.md | Disk-usage report. |
| Recovery.md | SQLite corruption/bloat safety and the automatic Recovery history. |
| Durable-Operations.md | Restart-safe jobs, leases, checkpoints, idempotency, external-service retries and recovery reporting. |
Why this exists
After an upgrade, several sites reported the login page showing "Must be logged
in", or — after login — the logo with "Loading, please wait." and a spinner that
never finished; pages took five or more minutes, the All Boards counts stayed at
0, and some labels showed raw i18n keys (e.g. allboards.starred). In top the
ferretdb process was pegged near 200% CPU for a long time. That is the FerretDB
v1 (SQLite) backend saturated under WeKan's poll load — often a migration/repair
still running, or simply a heavy instance on SQLite.
Problems → Status and snap run wekan.problems make that visible: an admin can now
see at a glance "a migration/repair is in progress; that is why logins are slow",
or "nothing is running; the backend itself is saturated — consider MongoDB", both
from the browser and from the server command line.
How this pane records what it sees
Design.md is the design behind the panes below: one summary row per problem rather than a row per event, the per-actor tally inside it, the IPv4 and IPv6 columns, and the API report, per-address login tally and blocking that are still being built. Read it if you are changing how Problems records things rather than what it shows.
The panes, in menu order
Every pane of this tab, in the order the menu shows them. The slug is what
the address uses: /admin/problems/<slug>.
Security, Delete and Notifications are no longer in this list: they moved to
Admin Panel / Settings (see The menu above).
| Menu path | URL slug | Page |
|---|---|---|
| Problems / Summary | summary |
Summary.md |
| Problems / Backup | backup |
Backup.md |
| Problems / Security Report | security-report |
Security-Report.md |
| Problems / Impersonation Report | impersonation |
Impersonation-Report.md |
| Problems / Password length | password-length |
Password-length.md |
| Problems / Performance | performance |
Performance.md |
| Problems / Speed | speed |
Speed.md |
| Problems / Tests | tests |
Tests.md |
| Problems / CPU usage | cpu |
CPU-usage.md |
| Problems / Memory Usage | ram |
RAM-usage.md |
| Problems / Disk usage | disk |
Disk-usage.md |
| Problems / Instrumentation | instrumentation |
Instrumentation.md |
| Problems / Broken Cards | broken-cards |
Broken-Cards.md |
| Problems / Files Report | files |
File-status.md |
| Problems / Rules Report | rules |
Rules-Report.md |
| Problems / Boards Report | boards |
Boards-Report.md |
| Problems / Cards Report | cards |
Cards-Report.md |
| Problems / Recovery | recovery |
Recovery.md |
| Problems / Offices | office |
Offices.md |
| Problems / API | api |
API.md |
| Problems / Database problems | database |
Database-problems.md |
| Problems / Filesystem integrity | integrity |
Filesystem-integrity.md |
| Problems / Email | mail |
Bounces.md |
0 of these 23 panes has no page of its own: every pane above links one. A pane added to the menu without a page gets a dash here and is counted in this sentence.
File status checks: inspect missing files, incomplete upload metadata, detected types, storage references and available recovery evidence.