Frontend Version do not match backend version! (1.19.0) #1667

Closed
opened 2026-02-28 02:28:55 -05:00 by deekerman · 1 comment
Owner

Originally created by @prohand on GitHub (Dec 23, 2022).

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

Hello,

I have a same error of this Issues : https://github.com/louislam/uptime-kuma/issues/2213
But i use the script : https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update
I have this problem since version 1.18.1

👟 Reproduction steps

Use this script to reproduce :

cd /opt/uptime-kuma/
git fetch --all
git checkout 1.19.0 --force
npm install --omit=dev
npm run download-dist
pm2 restart uptime-kuma

👀 Expected behavior

Fronted version = 1.19.0

😓 Actual Behavior

image

🐻 Uptime-Kuma Version

1.19.0

💻 Operating System and Arch

Ubuntu 22.04

🌐 Browser

Google Chrome

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

Downloading dist
https://github.com/louislam/uptime-kuma/releases/download/1.19.0/dist.tar.gz
https://objects.githubusercontent.com/github-production-release-asset-2e65be/382496361/25e6ee16-d9b9-4c2d-ba9a-29316ff1f3e4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20221223%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20221223T201821Z&X-Amz-Expires=300&X-Amz-Signature=c797efa8a235f83658d2e1bdddb4a7dfa163d83a8d4dfa65b9789f63bb941205&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=382496361&response-content-disposition=attachment%3B%20filename%3Ddist.tar.gz&response-content-type=application%2Foctet-stream
Extracting dist...
internal/fs/utils.js:332
    throw err;
    ^

Error: ENOTEMPTY: directory not empty, rename './dist' -> './dist-backup'
    at Object.renameSync (fs.js:798:3)
    at ClientRequest.<anonymous> (/opt/uptime-kuma/extra/download-dist.js:36:20)
    at Object.onceWrapper (events.js:520:26)
    at ClientRequest.emit (events.js:400:28)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:647:27)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17)
    at TLSSocket.socketOnData (_http_client.js:515:22)
    at TLSSocket.emit (events.js:400:28)
    at addChunk (internal/streams/readable.js:293:12)
    at readableAddChunk (internal/streams/readable.js:267:9) {
Originally created by @prohand on GitHub (Dec 23, 2022). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description Hello, I have a same error of this Issues : https://github.com/louislam/uptime-kuma/issues/2213 But i use the script : https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update I have this problem since version 1.18.1 ### 👟 Reproduction steps Use this script to reproduce : ``` cd /opt/uptime-kuma/ git fetch --all git checkout 1.19.0 --force npm install --omit=dev npm run download-dist pm2 restart uptime-kuma ``` ### 👀 Expected behavior Fronted version = 1.19.0 ### 😓 Actual Behavior ![image](https://user-images.githubusercontent.com/20227162/209402518-bcc917d7-6978-4a8f-9919-4298a1b215b0.png) ### 🐻 Uptime-Kuma Version 1.19.0 ### 💻 Operating System and Arch Ubuntu 22.04 ### 🌐 Browser Google Chrome ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output ```shell Downloading dist https://github.com/louislam/uptime-kuma/releases/download/1.19.0/dist.tar.gz https://objects.githubusercontent.com/github-production-release-asset-2e65be/382496361/25e6ee16-d9b9-4c2d-ba9a-29316ff1f3e4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20221223%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20221223T201821Z&X-Amz-Expires=300&X-Amz-Signature=c797efa8a235f83658d2e1bdddb4a7dfa163d83a8d4dfa65b9789f63bb941205&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=382496361&response-content-disposition=attachment%3B%20filename%3Ddist.tar.gz&response-content-type=application%2Foctet-stream Extracting dist... internal/fs/utils.js:332 throw err; ^ Error: ENOTEMPTY: directory not empty, rename './dist' -> './dist-backup' at Object.renameSync (fs.js:798:3) at ClientRequest.<anonymous> (/opt/uptime-kuma/extra/download-dist.js:36:20) at Object.onceWrapper (events.js:520:26) at ClientRequest.emit (events.js:400:28) at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:647:27) at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17) at TLSSocket.socketOnData (_http_client.js:515:22) at TLSSocket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) { ```
deekerman 2026-02-28 02:28:55 -05:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@prohand commented on GitHub (Dec 23, 2022):

I have solved this problem to add to this script ;) :

rm -r dist-backup
mv dist dist-backup

The new script is :

cd /opt/uptime-kuma/
rm -r dist-backup
mv dist dist-backup
git fetch --all
git checkout 1.19.0 --force
npm install --omit=dev
npm run download-dist
pm2 restart uptime-kuma
@prohand commented on GitHub (Dec 23, 2022): I have solved this problem to add to this script ;) : ``` rm -r dist-backup mv dist dist-backup ``` The new script is : ``` cd /opt/uptime-kuma/ rm -r dist-backup mv dist dist-backup git fetch --all git checkout 1.19.0 --force npm install --omit=dev npm run download-dist pm2 restart uptime-kuma ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#1667
No description provided.