SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-05-12 19:22:12 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

RustDesk install script gets stuck #967

New Issue
Closed
opened 2025-11-20 04:57:23 -05:00 by saavagebueno · 14 comments
saavagebueno commented 2025-11-20 04:57:23 -05:00
Owner
Copy Link

Originally created by @EnduringGuerila on GitHub (Apr 23, 2025).

✅ Have you read and understood the above guidelines?

yes

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

RustDesk

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Original issue with Advanced settings, then tested Default and get the same issue.

Verbose didn't display any extra info.

The script seems fine until after I select the storage option, then it gets stuck on "Updating LXC Template List " every time. It does only have 18GB of free storage, which isn't a ton but I thought that'd be enough for this tiny server.

  ⚙️  Using Default Settings on node pverouter (🔍  Verbose)
  🖥️  Operating System: debian
  🌟  Version: 12
  📦  Container Type: Unprivileged
  💾  Disk Size: 2 GB
  🧠  CPU Cores: 1
  🛠️  RAM Size: 512 MiB
  🆔  Container ID: 128
  🔍  Verbose Mode: Enabled
  🚀  Creating a RustDesk Server LXC using the above default settings
  
  ✔️  Using local for Template Storage.
  ✔️  Using local-lvm for Container Storage.
 ⠏ Updating LXC Template List

I let it run for 45 min before cancelling and trying other stuff.

🔄 Steps to reproduce the issue.

run script
select storage
fail

❌ Paste the full error output (if available).

Just in case it helps, this is what it shows when I ctrl+c

⠋^Ccurl: (22) The requested URL returned error: 400

[ERROR] in line 1336: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/create_lxc.sh)" $?

🖼️ Additional context (optional).

I updated and rebooted Proxmox just in case, no avail

Originally created by @EnduringGuerila on GitHub (Apr 23, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? RustDesk ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/rustdeskserver.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Original issue with Advanced settings, then tested Default and get the same issue. Verbose didn't display any extra info. The script seems fine until after I select the storage option, then it gets stuck on "Updating LXC Template List " every time. It does only have 18GB of free storage, which isn't a ton but I thought that'd be enough for this tiny server. ``` ⚙️ Using Default Settings on node pverouter (🔍 Verbose) 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 💾 Disk Size: 2 GB 🧠 CPU Cores: 1 🛠️ RAM Size: 512 MiB 🆔 Container ID: 128 🔍 Verbose Mode: Enabled 🚀 Creating a RustDesk Server LXC using the above default settings ✔️ Using local for Template Storage. ✔️ Using local-lvm for Container Storage. ⠏ Updating LXC Template List ``` I let it run for 45 min before cancelling and trying other stuff. ### 🔄 Steps to reproduce the issue. run script select storage fail ### ❌ Paste the full error output (if available). Just in case it helps, this is what it shows when I `ctrl+c` ``` ⠋^Ccurl: (22) The requested URL returned error: 400 [ERROR] in line 1336: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/create_lxc.sh)" $? ``` ### 🖼️ Additional context (optional). I updated and rebooted Proxmox just in case, no avail
saavagebueno added the bug label 2025-11-20 04:57:23 -05:00
saavagebueno commented 2025-11-20 04:57:24 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 23, 2025):

Thats Not the Script, its your Host. You cannot reach the Proxmox Repo. (pveam available etc.)

@MickLesk commented on GitHub (Apr 23, 2025): Thats Not the Script, its your Host. You cannot reach the Proxmox Repo. (pveam available etc.)
saavagebueno commented 2025-11-20 04:57:25 -05:00
Author
Owner
Copy Link

@EnduringGuerila commented on GitHub (Apr 23, 2025):

What do you mean I cannot reach the Proxmox Repo?
I just updated Proxmox (had the issue before and after the update)
and it had no issue hitting the repos

root@pverouter:~# apt update
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease                                                            
Hit:3 http://security.debian.org/debian-security bookworm-security InRelease                                             
Hit:4 http://download.proxmox.com/debian/pve bookworm InRelease                       
Reading package lists... Done                           
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

Image

@EnduringGuerila commented on GitHub (Apr 23, 2025): What do you mean I cannot reach the Proxmox Repo? I just updated Proxmox (had the issue before and after the update) and it had no issue hitting the repos ``` root@pverouter:~# apt update Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://security.debian.org/debian-security bookworm-security InRelease Hit:4 http://download.proxmox.com/debian/pve bookworm InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. ``` ![Image](https://github.com/user-attachments/assets/3bdb3730-16c4-4c80-9a6c-d16ca3ac9d1c)
saavagebueno commented 2025-11-20 04:57:25 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 23, 2025):

Something Block the Proxmox call for Templates. You cannot crawl this. Maybe reboot your system or Check your Network/DNS/AdBlock

@MickLesk commented on GitHub (Apr 23, 2025): Something Block the Proxmox call for Templates. You cannot crawl this. Maybe reboot your system or Check your Network/DNS/AdBlock
saavagebueno commented 2025-11-20 04:57:25 -05:00
Author
Owner
Copy Link

@SoPat712 commented on GitHub (Apr 23, 2025):

I'm having a similar issue

Image

Not sure what's going on, but I was making containers like 1 day ago, so...

@SoPat712 commented on GitHub (Apr 23, 2025): I'm having a similar issue ![Image](https://github.com/user-attachments/assets/0d7e67b1-41e7-4c85-93a0-89598c1f2ce0) Not sure what's going on, but I was making containers like 1 day ago, so...
saavagebueno commented 2025-11-20 04:57:25 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Apr 24, 2025):

You also have a error with you network on your host. Your host can not run pveam update to get the latest templates.

@michelroegl-brunner commented on GitHub (Apr 24, 2025): You also have a error with you network on your host. Your host can not run `pveam update` to get the latest templates.
saavagebueno commented 2025-11-20 04:57:25 -05:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Apr 24, 2025):

Yesterday github had a small outage I think, maybe it works again?

@CrazyWolf13 commented on GitHub (Apr 24, 2025): Yesterday github had a small outage I think, maybe it works again?
saavagebueno commented 2025-11-20 04:57:25 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Apr 24, 2025):

@CrazyWolf13 I dont think pveam is running against GH.

@michelroegl-brunner commented on GitHub (Apr 24, 2025): @CrazyWolf13 I dont think pveam is running against GH.
saavagebueno commented 2025-11-20 04:57:26 -05:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Apr 24, 2025):

@michelroegl-brunner No but @SoPat712 issue ^^

EDIT: oh nvm that's also pveam

@CrazyWolf13 commented on GitHub (Apr 24, 2025): @michelroegl-brunner No but @SoPat712 issue ^^ EDIT: oh nvm that's also pveam
saavagebueno commented 2025-11-20 04:57:26 -05:00
Author
Owner
Copy Link

@muthdieter commented on GitHub (Apr 24, 2025):

similar issue with all LXC normal VM are working

@muthdieter commented on GitHub (Apr 24, 2025): similar issue with all LXC normal VM are working
saavagebueno commented 2025-11-20 04:57:26 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 24, 2025):

Its an issue on your system, Not Script related. Disable AdBlock or something. Try an official DNS Server

@MickLesk commented on GitHub (Apr 24, 2025): Its an issue on your system, Not Script related. Disable AdBlock or something. Try an official DNS Server
saavagebueno commented 2025-11-20 04:57:26 -05:00
Author
Owner
Copy Link

@muthdieter commented on GitHub (Apr 24, 2025):

i tried

Cloudflare 1.1.1.1 -1.0.0.1
Google 8.8.8.8 -8.8.4.4
Quad9 9.9.9.9 -149.112.112.112
dns.watch 84.200.69.80 - 84.200.70.40

nothing always the same result -- so i think it is nor my dns -- maybee someting changes at the webside / a-record,...

@muthdieter commented on GitHub (Apr 24, 2025): i tried Cloudflare 1.1.1.1 -1.0.0.1 Google 8.8.8.8 -8.8.4.4 Quad9 9.9.9.9 -149.112.112.112 dns.watch 84.200.69.80 - 84.200.70.40 nothing always the same result -- so i think it is nor my dns -- maybee someting changes at the webside / a-record,...
saavagebueno commented 2025-11-20 04:57:26 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 24, 2025):

From Proxmox? Lol then have 100000 Users the Same issue. Its an simple pveam available and pvem download action

@MickLesk commented on GitHub (Apr 24, 2025): From Proxmox? Lol then have 100000 Users the Same issue. Its an simple pveam available and pvem download action
saavagebueno commented 2025-11-20 04:57:26 -05:00
Author
Owner
Copy Link

@EnduringGuerila commented on GitHub (Apr 24, 2025):

Working fine for me today...
I made no changes, just pressed the up arrow to rerun the same script.

@EnduringGuerila commented on GitHub (Apr 24, 2025): Working fine for me today... I made no changes, just pressed the up arrow to rerun the same script.
saavagebueno commented 2025-11-20 04:57:27 -05:00
Author
Owner
Copy Link

@ECP-Black commented on GitHub (May 9, 2025):

I had the same problem. It turned out (in my case) that the container id, wich I choosen, was already used.

@ECP-Black commented on GitHub (May 9, 2025): I had the same problem. It turned out (in my case) that the container id, wich I choosen, was already used.
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#967
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?