Impossible to install MeTube #1920

Closed
opened 2026-02-05 02:49:00 +03:00 by OVERLORD · 11 comments
Owner

Originally created by @erratumbuch on GitHub (Nov 2, 2025).

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?

9.0.11

📝 Provide a clear and concise description of the issue.

actually it is not possible to install metube lxc container.

error: Failed to fetch release metadata from https://api.github.com/repos/alexta69/metube/releases/latest after 3 attempts

🔄 Steps to reproduce the issue.

basic install.. always following issue:

error: Failed to fetch release metadata from https://api.github.com/repos/alexta69/metube/releases/latest after 3 attempts

Paste the full error output (if available).

✔️ Set up Container OS
✔️ Network Connected: XX.XXX.XXX.XX
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
✔️ Updated Container OS
✔️ Installed Dependencies
✔️ Setup uv 0.9.7
✔️ Setup Node.js 22
✔️ Installed Deno
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
✖️ Failed to fetch release metadata from https://api.github.com/repos/alexta69/metube/releases/latest after 3 attempts

[ERROR] in line 40: exit code 0: while executing command return 1

[ERROR] in line 1345: 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).

No response

Originally created by @erratumbuch on GitHub (Nov 2, 2025). ### ✅ 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? 9.0.11 ### 📝 Provide a clear and concise description of the issue. actually it is not possible to install metube lxc container. error: Failed to fetch release metadata from https://api.github.com/repos/alexta69/metube/releases/latest after 3 attempts ### 🔄 Steps to reproduce the issue. basic install.. always following issue: error: Failed to fetch release metadata from https://api.github.com/repos/alexta69/metube/releases/latest after 3 attempts ### ❌ Paste the full error output (if available). ✔️ Set up Container OS ✔️ Network Connected: XX.XXX.XXX.XX ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) ✔️ Updated Container OS ✔️ Installed Dependencies ✔️ Setup uv 0.9.7 ✔️ Setup Node.js 22 ✔️ Installed Deno curl: (22) The requested URL returned error: 404 curl: (22) The requested URL returned error: 404 curl: (22) The requested URL returned error: 404 ✖️ Failed to fetch release metadata from https://api.github.com/repos/alexta69/metube/releases/latest after 3 attempts [ERROR] in line 40: exit code 0: while executing command return 1 [ERROR] in line 1345: 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). _No response_
OVERLORD added the bug label 2026-02-05 02:49:00 +03:00
Author
Owner

@MickLesk commented on GitHub (Nov 2, 2025):

404 = forbidden/Not found. We Check it

@MickLesk commented on GitHub (Nov 2, 2025): 404 = forbidden/Not found. We Check it
Author
Owner

@tremor021 commented on GitHub (Nov 2, 2025):

All tarballs removed from repo @MickLesk

@tremor021 commented on GitHub (Nov 2, 2025): All tarballs removed from repo @MickLesk
Author
Owner

@MickLesk commented on GitHub (Nov 3, 2025):

Yes, the whole entrys removed. Then we need to remove the Script.

@MickLesk commented on GitHub (Nov 3, 2025): Yes, the whole entrys removed. Then we need to remove the Script.
Author
Owner

@alexta69 commented on GitHub (Nov 5, 2025):

Hi, author of MeTube here. I removed the GitHub Releases of MeTube, because they didn't reflect the actual release cycle. (Using GitHub releases was an experiment which I think didn't pan out.) The project automatically builds a docker image every time there's a yt-dlp update, and whenever any changes are merged to master -- these are the releases. So you can always use https://github.com/alexta69/metube/archive/refs/heads/master.zip as the latest version.
@MickLesk

@alexta69 commented on GitHub (Nov 5, 2025): Hi, author of MeTube here. I removed the GitHub Releases of MeTube, because they didn't reflect the actual release cycle. (Using GitHub releases was an experiment which I think didn't pan out.) The project automatically builds a docker image every time there's a yt-dlp update, and whenever any changes are merged to master -- these are the releases. So you can always use https://github.com/alexta69/metube/archive/refs/heads/master.zip as the latest version. @MickLesk
Author
Owner

@MickLesk commented on GitHub (Nov 6, 2025):

Hi @alexta69,

That's useless for us because we only use real “releases” through our internal tools. (fetch_and_deploy_gh_release)
=> We don't use Git Clone.
=> We don't use the latest from the branch itself (because the version identifier is simply missing).

Accordingly, it remains out of our collection.

@MickLesk commented on GitHub (Nov 6, 2025): Hi @alexta69, That's useless for us because we only use real “releases” through our internal tools. (fetch_and_deploy_gh_release) => We don't use Git Clone. => We don't use the latest from the branch itself (because the version identifier is simply missing). Accordingly, it remains out of our collection.
Author
Owner

@NaturalDevCR commented on GitHub (Nov 26, 2025):

Hi, author of MeTube here. I removed the GitHub Releases of MeTube, because they didn't reflect the actual release cycle. (Using GitHub releases was an experiment which I think didn't pan out.) The project automatically builds a docker image every time there's a yt-dlp update, and whenever any changes are merged to master -- these are the releases. So you can always use https://github.com/alexta69/metube/archive/refs/heads/master.zip as the latest version. @MickLesk

That's unfortunate... anyways, I'll have to install from source seems like.

@NaturalDevCR commented on GitHub (Nov 26, 2025): > Hi, author of MeTube here. I removed the GitHub Releases of MeTube, because they didn't reflect the actual release cycle. (Using GitHub releases was an experiment which I think didn't pan out.) The project automatically builds a docker image every time there's a yt-dlp update, and whenever any changes are merged to master -- these are the releases. So you can always use https://github.com/alexta69/metube/archive/refs/heads/master.zip as the latest version. [@MickLesk](https://github.com/MickLesk) That's unfortunate... anyways, I'll have to install from source seems like.
Author
Owner

@alexta69 commented on GitHub (Nov 29, 2025):

@MickLesk I've re-added releases to MeTube, in the hope that it will make it easier for people and projects that depend on them.

@alexta69 commented on GitHub (Nov 29, 2025): @MickLesk I've re-added releases to MeTube, in the hope that it will make it easier for people and projects that depend on them.
Author
Owner

@tremor021 commented on GitHub (Nov 29, 2025):

@alexta69 we relly on tagged releases as a way of versioning and recognizing releases that often have breaking changes in them, so we can pin the version installed in our scripts if we need to.

Trust me, its good for you too as this prevents people from making too many issues on your github, as we can quickly stop bad installs from happening. Its very common for a release to have a broken dependency or something so we have to revert to a previous version until issue is resolved.

Thanks for understanding.

@tremor021 commented on GitHub (Nov 29, 2025): @alexta69 we relly on tagged releases as a way of versioning and recognizing releases that often have breaking changes in them, so we can pin the version installed in our scripts if we need to. Trust me, its good for you too as this prevents people from making too many issues on your github, as we can quickly stop bad installs from happening. Its very common for a release to have a broken dependency or something so we have to revert to a previous version until issue is resolved. Thanks for understanding.
Author
Owner

@alexta69 commented on GitHub (Nov 29, 2025):

@tremor021 no problem, thanks. MeTube now has releases again, so it's possible to re-add it to Proxmox.

@alexta69 commented on GitHub (Nov 29, 2025): @tremor021 no problem, thanks. MeTube now has releases again, so it's possible to re-add it to Proxmox.
Author
Owner

@saif-sleek commented on GitHub (Dec 4, 2025):

@tremor021 @alexta69 Can we please re-add it to Proxmox?

@saif-sleek commented on GitHub (Dec 4, 2025): @tremor021 @alexta69 Can we please re-add it to Proxmox?
Author
Owner

@MickLesk commented on GitHub (Dec 4, 2025):

Create an Feature Request please.

@MickLesk commented on GitHub (Dec 4, 2025): Create an Feature Request please.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1920