New install: Admin area not loading and showing error
-
Fresh install of nodebb v4.2.0 on Ubuntu 22.04 with node v18.20.7. The forum appears fine, but when I log in as the admin user and go to the admin area, I just get a message:
Internal Error.
Oops! Looks like something went wrong!
Invalid Version: N/Alogs/output.log
shows this whenever I go to that page.2025-03-20T00:17:41.127Z [4567/1952357] - error: GET /admin TypeError: Invalid Version: N/A at new SemVer (/usr/local/share/nodebb/node_modules/semver/classes/semver.js:38:13) at compare (/usr/local/share/nodebb/node_modules/semver/functions/compare.js:3:32) at Object.gt (/usr/local/share/nodebb/node_modules/semver/functions/gt.js:2:29) at dashboardController.get (/usr/local/share/nodebb/src/controllers/admin/dashboard.js:36:45) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async /usr/local/share/nodebb/src/routes/helpers.js:80:5
I've tried re-running
nodebb build
and also completely re-installing. Any advice appreciated. -
Fresh install of nodebb v4.2.0 on Ubuntu 22.04 with node v18.20.7. The forum appears fine, but when I log in as the admin user and go to the admin area, I just get a message:
Internal Error.
Oops! Looks like something went wrong!
Invalid Version: N/Alogs/output.log
shows this whenever I go to that page.2025-03-20T00:17:41.127Z [4567/1952357] - error: GET /admin TypeError: Invalid Version: N/A at new SemVer (/usr/local/share/nodebb/node_modules/semver/classes/semver.js:38:13) at compare (/usr/local/share/nodebb/node_modules/semver/functions/compare.js:3:32) at Object.gt (/usr/local/share/nodebb/node_modules/semver/functions/gt.js:2:29) at dashboardController.get (/usr/local/share/nodebb/src/controllers/admin/dashboard.js:36:45) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async /usr/local/share/nodebb/src/routes/helpers.js:80:5
I've tried re-running
nodebb build
and also completely re-installing. Any advice appreciated.@Analog-Weapon thanks, looks like a backend error. Can you please open a GitHub issue?
We're not seeing it on our own installs.