starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 01:06:06 +03:00

[GH-ISSUE #11960] slskd "update" throws "✖️ You need to set 'CTID' variable." #2512

New issue

Closed

opened 2026-02-26 12:52:41 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 12:52:41 +03:00

Owner

Originally created by @M4ST3R-CTRL on GitHub (Feb 16, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11960

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

slskd

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

update

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.1/42db4a6cf33dac83 (running kernel: 6.17.2-1-pve)

📝 Provide a clear and concise description of the issue.

Running "update" for slskd seems to cause the same issue seen in https://github.com/community-scripts/ProxmoxVE/issues/11739

🔄 Steps to reproduce the issue.

run "update"

❌ Paste the full error output (if available).

✖️ You need to set 'CTID' variable.

🖼️ Additional context (optional).

No response

Originally created by @M4ST3R-CTRL on GitHub (Feb 16, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11960 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? slskd ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [ ] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.1.1/42db4a6cf33dac83 (running kernel: 6.17.2-1-pve) ### 📝 Provide a clear and concise description of the issue. Running "update" for slskd seems to cause the same issue seen in https://github.com/community-scripts/ProxmoxVE/issues/11739 ### 🔄 Steps to reproduce the issue. run "update" ### ❌ Paste the full error output (if available). ✖️ You need to set 'CTID' variable. ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:52:41 +03:00

closed this issue
added the
🛑 Failure to comply with the guidelines
label

kerem commented

2026-02-26 12:52:42 +03:00

Author

Owner

@vhsdream commented on GitHub (Feb 16, 2026):

If you don't provide the info we ask for, then it makes it very difficult for us to help. Please provide all the information you can: verbose logs, environment info, how many times you tried updating, etc.

@vhsdream commented on GitHub (Feb 16, 2026): If you don't provide the info we ask for, then it makes it very difficult for us to help. Please provide all the information you can: verbose logs, environment info, how many times you tried updating, etc.

kerem commented

2026-02-26 12:52:42 +03:00

Author

Owner

@M4ST3R-CTRL commented on GitHub (Feb 16, 2026):

If you don't provide the info we ask for, then it makes it very difficult for us to help. Please provide all the information you can: verbose logs, environment info, how many times you tried updating, etc.

Sorry, I don't know what you need that I failed to provide? I've provided the error listed in verbose mode that caused the update script to fail, the container os, and the proxmox version. I attempted 3-4 times with the same error, as well as linked to a now-resolved issue for another lxc that displayed the same behavior.

@M4ST3R-CTRL commented on GitHub (Feb 16, 2026): > If you don't provide the info we ask for, then it makes it very difficult for us to help. Please provide all the information you can: verbose logs, environment info, how many times you tried updating, etc. Sorry, I don't know what you need that I failed to provide? I've provided the error listed in verbose mode that caused the update script to fail, the container os, and the proxmox version. I attempted 3-4 times with the same error, as well as linked to a now-resolved issue for another lxc that displayed the same behavior.

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/ProxmoxVE#2512

No description provided.

Rows
Columns