Updating metube Fails with curl: (22) The requested URL returned error: 403

[TheMagnetar]

✅ 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?

update

⚙️ 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.

When updating the LXC container, it fails with:

curl: (22) The requested URL returned error: 403

[ERROR] in line 1146: exit code 0: while executing command LATEST_VERSION=$(curl -fsSL https://api.github.com/repos/astral-sh/uv/releases/latest | grep '"tag_name":' | cut -d '"' -f4 | sed 's/^v//')

🔄 Steps to reproduce the issue.

Call the update script

❌ Paste the full error output (if available).

curl: (22) The requested URL returned error: 403

[ERROR] in line 1146: exit code 0: while executing command LATEST_VERSION=$(curl -fsSL https://api.github.com/repos/astral-sh/uv/releases/latest | grep '"tag_name":' | cut -d '"' -f4 | sed 's/^v//')

🖼️ Additional context (optional).

No response

[MickLesk]

Your Network Block UV Repo from astral

[TheMagnetar]

No. Only when using the script. On a web browser in the same VLAN i can access "https://api.github.com/repos/astral-sh/uv/releases/latest"

[tremor021]

Then you file a complain to curl devs for falsely accusing your network for malfunctioning or blocking access, because its surely not a fault on your end

[tremor021]

@TheMagnetar this is how it goes on a host that has no network issues:

[MickLesk]

Tremor is right. Call the unfinished LXC with pct enter and execute the call, you will see that it does not work. You can't assume other devices because an LXC is part of a host but uses an encapsulated/separate network. And that's where something is wrong.

Incidentally, we have switched to curl to get better outputs and 403 is clear.

[tremor021]

Either host network issue or API limits reached

[TheMagnetar]

API limit was the cause