starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Update MeTube #1868

New Issue
Closed
opened 2026-02-05 02:29:52 +03:00 by OVERLORD · 11 comments
OVERLORD commented 2026-02-05 02:29:52 +03:00
Owner
Copy Link

Originally created by @Space010 on GitHub (Oct 23, 2025).

Originally assigned to: @MickLesk, @tremor021 on GitHub.

✅ Have you read and understood the above guidelines?

yes

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

MeTube

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

8.4.14

📝 Provide a clear and concise description of the issue.

When trying to update MeTube with the "update" command nothing happens and it just shows a error message.

🔄 Steps to reproduce the issue.

enter "update" into the MeTube LXC console

❌ Paste the full error output (if available).

Image

🖼️ Additional context (optional).

No response

Originally created by @Space010 on GitHub (Oct 23, 2025). Originally assigned to: @MickLesk, @tremor021 on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? MeTube ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/metube.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 8.4.14 ### 📝 Provide a clear and concise description of the issue. When trying to update MeTube with the "update" command nothing happens and it just shows a error message. ### 🔄 Steps to reproduce the issue. enter "update" into the MeTube LXC console ### ❌ Paste the full error output (if available). <img width="663" height="170" alt="Image" src="https://github.com/user-attachments/assets/48b31f70-69d7-4152-93f1-73afe6691c07" /> ### 🖼️ Additional context (optional). _No response_
OVERLORD added the buginvestigation labels 2026-02-05 02:29:52 +03:00
OVERLORD commented 2026-02-05 02:29:58 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 23, 2025):

are you using console with pct enter <lxcid>?

@tremor021 commented on GitHub (Oct 23, 2025): are you using console with `pct enter <lxcid>`?
OVERLORD commented 2026-02-05 02:30:03 +03:00
Author
Owner
Copy Link

@Space010 commented on GitHub (Oct 23, 2025):

no, I open the Proxmox GUI and choose the MeTube LXC, then I just type update.

Image
@Space010 commented on GitHub (Oct 23, 2025): no, I open the Proxmox GUI and choose the MeTube LXC, then I just type update. <img width="876" height="270" alt="Image" src="https://github.com/user-attachments/assets/1d1af090-4e98-4f14-9250-e0ef544e9158" />
OVERLORD commented 2026-02-05 02:30:34 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 23, 2025):

can you please do cat ~/.bashrc

@tremor021 commented on GitHub (Oct 23, 2025): can you please do `cat ~/.bashrc`
OVERLORD commented 2026-02-05 02:31:06 +03:00
Author
Owner
Copy Link

@Space010 commented on GitHub (Oct 23, 2025):

# ~/.bashrc: executed by bash(1) for non-login shells.

# Note: PS1 and umask are already set in /etc/profile. You should not
# need this unless you want different defaults for root.
# PS1='${debian_chroot:+($debian_chroot)}\h:\w\$ '
# umask 022

# You may uncomment the following lines if you want `ls' to be colorized:
# export LS_OPTIONS='--color=auto'
# eval "$(dircolors)"
# alias ls='ls $LS_OPTIONS'
# alias ll='ls $LS_OPTIONS -l'
# alias l='ls $LS_OPTIONS -lA'
#
# Some more alias to avoid making mistakes:
# alias rm='rm -i'
# alias cp='cp -i'
# alias mv='mv -i'

# uv
export PATH="/root/.local/bin:$PATH"
. "/usr/local/env"export TERM='xterm-256color'
export PATH="/usr/local/bin:$PATH"
export PATH="/usr/local/bin:$PATH"
export PATH="/usr/local/bin:$PATH"
export PATH="/usr/local/bin:$PATH"
export PATH="/usr/local/bin:$PATH"
export PATH="/usr/local/bin:$PATH"
export PATH="/usr/local/bin:$PATH"
export PATH="/usr/local/bin:$PATH"
export PATH="/usr/local/bin:$PATH"
export PATH="/usr/local/bin:$PATH"
export PATH="/usr/local/bin:$PATH"```
@Space010 commented on GitHub (Oct 23, 2025): ```root@metube:~# cat ~/.bashrc # ~/.bashrc: executed by bash(1) for non-login shells. # Note: PS1 and umask are already set in /etc/profile. You should not # need this unless you want different defaults for root. # PS1='${debian_chroot:+($debian_chroot)}\h:\w\$ ' # umask 022 # You may uncomment the following lines if you want `ls' to be colorized: # export LS_OPTIONS='--color=auto' # eval "$(dircolors)" # alias ls='ls $LS_OPTIONS' # alias ll='ls $LS_OPTIONS -l' # alias l='ls $LS_OPTIONS -lA' # # Some more alias to avoid making mistakes: # alias rm='rm -i' # alias cp='cp -i' # alias mv='mv -i' # uv export PATH="/root/.local/bin:$PATH" . "/usr/local/env"export TERM='xterm-256color' export PATH="/usr/local/bin:$PATH" export PATH="/usr/local/bin:$PATH" export PATH="/usr/local/bin:$PATH" export PATH="/usr/local/bin:$PATH" export PATH="/usr/local/bin:$PATH" export PATH="/usr/local/bin:$PATH" export PATH="/usr/local/bin:$PATH" export PATH="/usr/local/bin:$PATH" export PATH="/usr/local/bin:$PATH" export PATH="/usr/local/bin:$PATH" export PATH="/usr/local/bin:$PATH"```
OVERLORD commented 2026-02-05 02:32:18 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 23, 2025):

Yes, this is typo in the install script... Path is not appended properly to the end of ~/.bashrc

Quick fix so you dont have to wait for updated script is, correct this line:

. "/usr/local/env"export TERM='xterm-256color'

to be:

. "/usr/local/env"
export TERM='xterm-256color'

and leave only one of these lines, you can delete the duplicates:

export PATH="/usr/local/bin:$PATH"

after you save the file, do:

source ~/.bashrc

then type update

@tremor021 commented on GitHub (Oct 23, 2025): Yes, this is typo in the install script... Path is not appended properly to the end of `~/.bashrc` Quick fix so you dont have to wait for updated script is, correct this line: `. "/usr/local/env"export TERM='xterm-256color'` to be: ``` . "/usr/local/env" export TERM='xterm-256color' ``` and leave only one of these lines, you can delete the duplicates: `export PATH="/usr/local/bin:$PATH"` after you save the file, do: `source ~/.bashrc` then type `update`
OVERLORD commented 2026-02-05 02:32:45 +03:00
Author
Owner
Copy Link

@Space010 commented on GitHub (Oct 23, 2025):

Now this error shows up:
Image

@Space010 commented on GitHub (Oct 23, 2025): Now this error shows up: <img width="1031" height="292" alt="Image" src="https://github.com/user-attachments/assets/3f943d1d-b99f-41eb-bb1b-daf69ff6b105" />
OVERLORD commented 2026-02-05 02:34:21 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 23, 2025):

Well this is not a error from update script. This is something in our backend. We need to investigate this

@tremor021 commented on GitHub (Oct 23, 2025): Well this is not a error from update script. This is something in our backend. We need to investigate this
OVERLORD commented 2026-02-05 02:34:57 +03:00
Author
Owner
Copy Link

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

How you run Update?

Exit missing, Tremor add it in His pr

@MickLesk commented on GitHub (Oct 23, 2025): How you run Update? Exit missing, Tremor add it in His pr
OVERLORD commented 2026-02-05 02:35:27 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 23, 2025):

Added

@tremor021 commented on GitHub (Oct 23, 2025): Added
OVERLORD commented 2026-02-05 02:36:12 +03:00
Author
Owner
Copy Link

@Space010 commented on GitHub (Oct 23, 2025):

Is there a quickfix for me, or should I just wait. I don't need this right away.. I can wait.

thanks for the fast help

@Space010 commented on GitHub (Oct 23, 2025): Is there a quickfix for me, or should I just wait. I don't need this right away.. I can wait. thanks for the fast help
OVERLORD commented 2026-02-05 02:36:15 +03:00
Author
Owner
Copy Link

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

Now you can run Update again

@MickLesk commented on GitHub (Oct 23, 2025): Now you can run Update again
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug investigation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1868
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?