SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Uptime Kuma: Error when executing installation script #1366

New Issue
Closed
opened 2025-11-20 05:08:56 -05:00 by saavagebueno · 10 comments
saavagebueno commented 2025-11-20 05:08:56 -05:00
Owner
Copy Link

Originally created by @NORiiS on GitHub (Jun 27, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Uptime Kuma

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/uptimekuma.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📝 Provide a clear and concise description of the issue.

Hello,
first of all thank you for providing so many useful and easy to use enhancements! I already installed a few of time successfully.

However when I go in to my proxmox VE Shell to instsall Uptime Kuma I run into an error:

🔄 Steps to reproduce the issue.

Step 1: Go into proxmox Shell
Step 2: Paste the Script and press Enter
Step 3: Either Default Settings or Default Settings (with verbose). It fails in both cases

❌ Paste the full error output (if available).

mv: cannot move 'uptime-kuma' to a subdirectory of itself, '/opt/uptime-kuma/uptime-kuma'

[ERROR] in line 25: exit code 0: while executing command mv uptime-kuma /opt/uptime-kuma

[ERROR] in line 1088: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/"var_install".sh)" ?

🖼️ Additional context (optional).

It worked for a couple of other helper scripts, this was the first one that threw an error.

Originally created by @NORiiS on GitHub (Jun 27, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Uptime Kuma ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/uptimekuma.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. Hello, first of all thank you for providing so many useful and easy to use enhancements! I already installed a few of time successfully. However when I go in to my proxmox VE Shell to instsall Uptime Kuma I run into an error: ### 🔄 Steps to reproduce the issue. Step 1: Go into proxmox Shell Step 2: Paste the Script and press Enter Step 3: Either Default Settings or Default Settings (with verbose). It fails in both cases ### ❌ Paste the full error output (if available). mv: cannot move 'uptime-kuma' to a subdirectory of itself, '/opt/uptime-kuma/uptime-kuma' [ERROR] in line 25: exit code 0: while executing command mv uptime-kuma /opt/uptime-kuma [ERROR] in line 1088: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/"$var_install".sh)" $? ### 🖼️ Additional context (optional). It worked for a couple of other helper scripts, this was the first one that threw an error.
saavagebueno added the bug label 2025-11-20 05:08:56 -05:00
saavagebueno commented 2025-11-20 05:08:57 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 27, 2025):

Cant reproduce. Its an Git Clone and it Work fine.

@MickLesk commented on GitHub (Jun 27, 2025): Cant reproduce. Its an Git Clone and it Work fine.
saavagebueno commented 2025-11-20 05:08:57 -05:00
Author
Owner
Copy Link

@castanea-dentata commented on GitHub (Jun 27, 2025):

I also have this same exact error as well.

mv: cannot move 'uptime-kuma' to a subdirectory of itself, '/opt/uptime-kuma/uptime-kuma'

[ERROR] in line 25: exit code 0: while executing command mv uptime-kuma /opt/uptime-kuma

[ERROR] in line 1088: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/"var_install".sh)" ?

@castanea-dentata commented on GitHub (Jun 27, 2025): I also have this same exact error as well. mv: cannot move 'uptime-kuma' to a subdirectory of itself, '/opt/uptime-kuma/uptime-kuma' [ERROR] in line 25: exit code 0: while executing command mv uptime-kuma /opt/uptime-kuma [ERROR] in line 1088: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/"$var_install".sh)" $?
saavagebueno commented 2025-11-20 05:08:57 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 27, 2025):

Then Run in verbose

@MickLesk commented on GitHub (Jun 27, 2025): Then Run in verbose
saavagebueno commented 2025-11-20 05:08:58 -05:00
Author
Owner
Copy Link

@castanea-dentata commented on GitHub (Jun 27, 2025):

That error is from running in verbose. No other errors are shown.

@castanea-dentata commented on GitHub (Jun 27, 2025): That error is from running in verbose. No other errors are shown.
saavagebueno commented 2025-11-20 05:08:58 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 27, 2025):

And the Git Output?

@MickLesk commented on GitHub (Jun 27, 2025): And the Git Output?
saavagebueno commented 2025-11-20 05:08:58 -05:00
Author
Owner
Copy Link

@castanea-dentata commented on GitHub (Jun 27, 2025):

Installing Uptime KumaCloning into 'uptime-kuma'...
remote: Enumerating objects: 34871, done.
remote: Counting objects: 100% (36/36), done.
remote: Compressing objects: 100% (32/32), done.
remote: Total 34871 (delta 20), reused 4 (delta 4), pack-reused 34835 (from 3)
Receiving objects: 100% (34871/34871), 28.13 MiB | 18.07 MiB/s, done.
Resolving deltas: 100% (26430/26430), done.
mv: cannot move 'uptime-kuma' to a subdirectory of itself, '/opt/uptime-kuma/uptime-kuma'

[ERROR] in line 25: exit code 0: while executing command mv uptime-kuma /opt/uptime-kuma

[ERROR] in line 1088: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/"var_install".sh)" ?

@castanea-dentata commented on GitHub (Jun 27, 2025): Installing Uptime KumaCloning into 'uptime-kuma'... remote: Enumerating objects: 34871, done. remote: Counting objects: 100% (36/36), done. remote: Compressing objects: 100% (32/32), done. remote: Total 34871 (delta 20), reused 4 (delta 4), pack-reused 34835 (from 3) Receiving objects: 100% (34871/34871), 28.13 MiB | 18.07 MiB/s, done. Resolving deltas: 100% (26430/26430), done. mv: cannot move 'uptime-kuma' to a subdirectory of itself, '/opt/uptime-kuma/uptime-kuma' [ERROR] in line 25: exit code 0: while executing command mv uptime-kuma /opt/uptime-kuma [ERROR] in line 1088: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/"$var_install".sh)" $?
saavagebueno commented 2025-11-20 05:08:58 -05:00
Author
Owner
Copy Link

@castanea-dentata commented on GitHub (Jun 27, 2025):

If I make a Debian LXC on proxmox, then git clone UptimeKuma repository and then install via npm, it works fine.

@castanea-dentata commented on GitHub (Jun 27, 2025): If I make a Debian LXC on proxmox, then git clone UptimeKuma repository and then install via npm, it works fine.
saavagebueno commented 2025-11-20 05:08:58 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 27, 2025):

I take a Look at monday again, my Install work

@MickLesk commented on GitHub (Jun 27, 2025): I take a Look at monday again, my Install work
saavagebueno commented 2025-11-20 05:08:58 -05:00
Author
Owner
Copy Link

@lucacome commented on GitHub (Jun 27, 2025):

I'm seeing the same error

  ⠙   Installing Uptime Kumamv: cannot move 'uptime-kuma' to a subdirectory of itself, '/opt/uptime-kuma/uptime-kuma'
  ⠹   Installing Uptime Kuma
[ERROR] in line 25: exit code 0: while executing command mv uptime-kuma /opt/uptime-kuma

[ERROR] in line 1088: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/"$var_install".sh)" $?
@lucacome commented on GitHub (Jun 27, 2025): I'm seeing the same error ``` ⠙ Installing Uptime Kumamv: cannot move 'uptime-kuma' to a subdirectory of itself, '/opt/uptime-kuma/uptime-kuma' ⠹ Installing Uptime Kuma [ERROR] in line 25: exit code 0: while executing command mv uptime-kuma /opt/uptime-kuma [ERROR] in line 1088: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/"$var_install".sh)" $? ```
saavagebueno commented 2025-11-20 05:08:58 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 28, 2025):

Yeah thats the perfect hint. So i get it. Fixed

@MickLesk commented on GitHub (Jun 28, 2025): Yeah thats the perfect hint. So i get it. Fixed
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1366
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?