Should npm ci be used instead of npm install to make sure it's deterministic? (To try and avoid any dep injection).
Search Criteria
Package Details: uptime-kuma 2.5.3-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/uptime-kuma.git (read-only, click to copy) |
|---|---|
| Package Base: | uptime-kuma |
| Description: | A fancy self-hosted monitoring tool |
| Upstream URL: | https://github.com/louislam/uptime-kuma |
| Licenses: | MIT |
| Submitter: | sylvaindurand |
| Maintainer: | matth |
| Last Packager: | matth |
| Votes: | 10 |
| Popularity: | 0.195475 |
| First Submitted: | 2021-10-15 20:47 (UTC) |
| Last Updated: | 2026-08-27 13:45 (UTC) |
Dependencies (2)
- nodejs (nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogenAUR, nodejs-lts-iron, nodejs-lts-jod, nodejs-lts-krypton)
- npm (npm-corepackAUR, python-nodejs-wheelAUR) (make)
Required by (1)
Sources (5)
fermino commented on 2026-06-04 04:24 (UTC)
pfonks commented on 2026-05-07 17:24 (UTC)
@matth npm install sqlite3 was run during service startup. The solution was to run
npm install --include=dev
npm rebuild
in /usr/lib/node_modules/uptime-kuma
matth commented on 2026-05-07 15:05 (UTC)
@pfonks No issues running it here. Why are you running npm install of sqlite3? How did you build the package?
pfonks commented on 2026-05-07 07:12 (UTC) (edited on 2026-05-07 08:26 (UTC) by pfonks)
After updating I get the following error during service startup:
$ npm install sqlite3 --save
Cannot find module '/usr/lib/node_modules/uptime-kuma/node_modules/@louislam/sqlite3/lib/binding/napi-v6-linux-x64/node_sqlite3.node'
Ape commented on 2026-01-17 10:22 (UTC)
The default config.env in the package should not include these lines:
UPTIME_KUMA_HOST=127.0.0.1
UPTIME_KUMA_PORT=3001
3001 is the default port anyway, so it doesn't do anything. More importantly, the default host is ::. Setting it to 127.0.0.1 is just worse.
matth commented on 2025-12-25 11:53 (UTC)
This is now updated to 2.x
2 major changes are:
Set it to run under the user `uptime-kuma` instead of `root`.
Set the data dir to `/var/lib/uptime-kuma` instead of `/usr/lib/node_modules/uptime-kuma/data`
If you are upgrading from 1.x and have existing data you can stop the server and move the data before updating mv /usr/lib/node_modules/uptime-kuma/data /var/lib/uptime-kuma
See the migration guide for other details https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2
You can also edit what the data dir is by editing /etc/uptime-kuma/config.env
See the documentation for other environment variables that can be set: https://github.com/louislam/uptime-kuma/wiki/Environment-Variables
matth commented on 2025-12-15 23:43 (UTC) (edited on 2025-12-15 23:43 (UTC) by matth)
I have created an update for this for version 2.0.2 https://codeberg.org/matt/aur-pkgbuilds/src/branch/main/uptime-kuma
2 changes I have made are:
-
Set it to run under the user uptime-kuma instead of root.
-
Set the data dir to
/var/lib/uptime-kumainstead of/usr/lib/node_modules/uptime-kuma/data
If you are upgrading and have existing data you can stop the server and move the data before updating mv /usr/lib/node_modules/uptime-kuma/data /var/lib/uptime-kuma
See the migration guide for other details https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2
axzxc1236 commented on 2025-11-02 09:58 (UTC)
If you encounter "TypeError: Cannot read properties of undefined (reading 'prototype')", downgrade nodejs to 24.9.0.
thomzane commented on 2025-09-17 15:07 (UTC)
uptime-kuma broke for me somewhat recently due to a node dependency update. I seem to have needed to do this before at some point as well.
node version
node: error while loading shared libraries: libsimdjson.so.26: cannot open shared object file: No such file or directory
This solution of symlinking specific versions is not great, but it worked.
sudo ln -s /lib/libsimdjson.so /usr/lib/libsimdjson.so.26
Test
node --version
v23.11.1
Then the uptime-kuma service was able to launch again.
Pinned Comments
matth commented on 2025-12-25 11:53 (UTC)
This is now updated to 2.x
2 major changes are:
If you are upgrading from 1.x and have existing data you can stop the server and move the data before updating
mv /usr/lib/node_modules/uptime-kuma/data /var/lib/uptime-kumaSee the migration guide for other details https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2
You can also edit what the data dir is by editing
/etc/uptime-kuma/config.envSee the documentation for other environment variables that can be set: https://github.com/louislam/uptime-kuma/wiki/Environment-Variables
bgh commented on 2023-04-17 14:11 (UTC)
Note: a service restart may be required if the web interface is inaccessible after updating