[Immich] Could not fetch latest uv version from GitHub API

[frontend-report]

Script: Immich

Reported by: @foxtrotierra6829

Guidelines

• Read and understood guidelines: yes
• Verbose mode used: yes

Issue occurs during: Initial Creation / Installation

Environment

• Linux distribution: Debian
• Proxmox version: 8.4
• Default settings: No
• Advanced settings: Yes
• Exact command: bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/immich.sh)"

Description

Despite using the Gitea version of the script, at 5 tries at different times every time the script fails at fetching content from GitHub.

The GitHub dependencies should either be removed from the Gitea script or a personal token should be allowed to be set to avoid being timed out.

Steps to reproduce

• paste GitHub or Gitea version of the script into the Proxmox host shell
• run through wizard
• fails at fetching content from GitHub

Error output

Processing triggers for libc-bin (2.41-12+deb13u2) ...
[2026-05-09 12:36:41] [OK] Installed packages from Debian Testing repo
[2026-05-09 12:36:42] [ERROR] Could not fetch latest uv version from GitHub API
[2026-05-09 12:36:42] [ERROR] in line 149: exit code 7 (curl: Failed to connect (network unreachable / host down)): while executing command return 7

✖️ Installation failed in container 122 (exit code: 7)
📋 Installation log: /tmp/immich-122-22f4361f.log

Error: curl: Failed to connect (network unreachable / host down)

[FoxtrotSierra6829]

Typo in the username, it's me

[MickLesk]

Yeah because your system Block the calls against UV? Gitea is just an mirror. We cant remove GitHub Scripts inside that are only available with GitHub lol @FoxtrotSierra6829 the Output is clear, Host unreachable inside the LXC -> nothing cant work either our functions or uv, or Release calls, or tarballs.

[FoxtrotSierra6829]

It is not unreachable:

✔️ IPv4 Internet Connected
✔️ IPv6 Internet Connected
✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )

In the host shell, after terminating the script

In the LXC, kept for debugging:

[FoxtrotSierra6829]

What is more likely IMO, is that the API did not return the expected result because it was rate limited because it's unauthenticated. Which is why I am asking to either not rely on scripts that are hosted on GitHub when using the Gitea version of the script, or to be able to provide a GitHub API key.

From your site:

When to use Gitea: GitHub may have issues including slow connections, delayed updates after bug fixes, no IPv6 support, API rate limits (60/hour). Use our Gitea mirror as a reliable alternative when experiencing these issues.

[MickLesk]

Yeah and where is the UV gitea Repo? ^^

[FoxtrotSierra6829]

Well it's available both as MIT and as Apache 2.0, so it would be possible to host a fork elsewhere, but still, the alternative I am asking for is to be able to provide a GitHub API key

[MickLesk]

var_github_token

[michelroegl-brunner]

What is more likely IMO, is that the API did not return the expected result because it was rate limited because it's unauthenticated. Which is why I am asking to either not rely on scripts that are hosted on GitHub when using the Gitea version of the script, or to be able to provide a GitHub API key.

From your site:

When to use Gitea: GitHub may have issues including slow connections, delayed updates after bug fixes, no IPv6 support, API rate limits (60/hour). Use our Gitea mirror as a reliable alternative when experiencing these issues.

We will not host mirrors of all apps on our gitea.