SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Homarr - Installation Fails Due to Repository Connection Errors #1660

New Issue
Closed
opened 2025-11-20 05:14:23 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 05:14:23 -05:00
Owner
Copy Link

Originally created by @vicentecandido on GitHub (Aug 8, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Homarr

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

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

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

Hi, I'm trying to install Homarr using the Proxmox community scripts on a Debian 12 LXC container (ID: 124) running on Proxmox. The setup process fails with errors related to connecting to Debian repositories. Below is the relevant error output:

🔄 Steps to reproduce the issue.

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

❌ Paste the full error output (if available).

                                        
  ⚙️  Using Default Settings on node pve-03-notebranco (🔍  Verbose)
  🆔  Container ID: 124
  🖥️  Operating System: debian (12)
  📦  Container Type: Unprivileged
  💾  Disk Size: 8 GB
  🧠  CPU Cores: 3
  🛠️  RAM Size: 6144 MiB
  🔍  Verbose Mode: Enabled
  🚀  Creating a homarr LXC using the above default settings
  
  ✔️   Valid Storage Found
 
  ✔️   Validated Storage | Container: local (Free: 310.4GB  Used: 92.5GB)
storage 'proxmox_share' is not online
  ✔️   Cluster is quorate
  ✔️   LXC Template List Updated
  ✔️   LXC Template 'debian-12-standard_12.7-1_amd64.tar.zst' is ready to use.
  ✔️   LXC Container 124 was successfully created.
  ✔️   Started LXC Container
   💡   No network in LXC yet (try 1/10) – waiting...
  ✔️   Network in LXC is reachable (ping)
  ✔️   Customized LXC Container
  ✔️   Set up Container OS
  ✔️   Network Connected: 192.168.0.246 
  ✔️   IPv4 Internet Connected
   ✖️   IPv6 Internet Not Connected
  ✔️   Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
Ign:1 http://deb.debian.org/debian bookworm InRelease
Ign:2 http://deb.debian.org/debian bookworm-updates InRelease
Err:3 http://deb.debian.org/debian bookworm Release
  Cannot initiate the connection to deb.debian.org:80 (2a04:4e42::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:200::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:400::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:600::644). - connect (101: Network is unreachable)
Err:4 http://deb.debian.org/debian bookworm-updates Release
  Cannot initiate the connection to deb.debian.org:80 (2a04:4e42::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:200::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:400::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:600::644). - connect (101: Network is unreachable)
Ign:5 http://security.debian.org bookworm-security InRelease
Err:6 http://security.debian.org bookworm-security Release
  Cannot initiate the connection to security.debian.org:80 (2a04:4e42:200::644). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:600::644). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42::644). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:400::644). - connect (101: Network is unreachable)
Reading package lists... Done
E: The repository 'http://deb.debian.org/debian bookworm Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian bookworm-updates Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://security.debian.org bookworm-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

[ERROR] in line 145: exit code 0: while executing command $STD apt-get update

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

Image
Originally created by @vicentecandido on GitHub (Aug 8, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Homarr ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Hi, I'm trying to install Homarr using the Proxmox community scripts on a Debian 12 LXC container (ID: 124) running on Proxmox. The setup process fails with errors related to connecting to Debian repositories. Below is the relevant error output: ### 🔄 Steps to reproduce the issue. bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh)" ### ❌ Paste the full error output (if available). ``` ⚙️ Using Default Settings on node pve-03-notebranco (🔍 Verbose) 🆔 Container ID: 124 🖥️ Operating System: debian (12) 📦 Container Type: Unprivileged 💾 Disk Size: 8 GB 🧠 CPU Cores: 3 🛠️ RAM Size: 6144 MiB 🔍 Verbose Mode: Enabled 🚀 Creating a homarr LXC using the above default settings ✔️ Valid Storage Found ✔️ Validated Storage | Container: local (Free: 310.4GB Used: 92.5GB) storage 'proxmox_share' is not online ✔️ Cluster is quorate ✔️ LXC Template List Updated ✔️ LXC Template 'debian-12-standard_12.7-1_amd64.tar.zst' is ready to use. ✔️ LXC Container 124 was successfully created. ✔️ Started LXC Container 💡 No network in LXC yet (try 1/10) – waiting... ✔️ Network in LXC is reachable (ping) ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.0.246 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) Ign:1 http://deb.debian.org/debian bookworm InRelease Ign:2 http://deb.debian.org/debian bookworm-updates InRelease Err:3 http://deb.debian.org/debian bookworm Release Cannot initiate the connection to deb.debian.org:80 (2a04:4e42::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:200::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:400::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:600::644). - connect (101: Network is unreachable) Err:4 http://deb.debian.org/debian bookworm-updates Release Cannot initiate the connection to deb.debian.org:80 (2a04:4e42::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:200::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:400::644). - connect (101: Network is unreachable) Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:600::644). - connect (101: Network is unreachable) Ign:5 http://security.debian.org bookworm-security InRelease Err:6 http://security.debian.org bookworm-security Release Cannot initiate the connection to security.debian.org:80 (2a04:4e42:200::644). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:600::644). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42::644). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:400::644). - connect (101: Network is unreachable) Reading package lists... Done E: The repository 'http://deb.debian.org/debian bookworm Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://deb.debian.org/debian bookworm-updates Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://security.debian.org bookworm-security Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. [ERROR] in line 145: exit code 0: while executing command $STD apt-get update [ERROR] in line 1353: 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). <img width="382" height="155" alt="Image" src="https://github.com/user-attachments/assets/3243c80d-7633-4091-b08c-dea966dfbf18" />
saavagebueno added the bug label 2025-11-20 05:14:23 -05:00
saavagebueno commented 2025-11-20 05:14:23 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 8, 2025):

Your ipv6 config failed, that try to reach Debian repo, but Debian repo is only reachable over ipv4 (no upstream for ipv6)

Disable ipv6 and try again or reboot your ISP/Network/DHCP If you dont get an correct ipv4

@MickLesk commented on GitHub (Aug 8, 2025): Your ipv6 config failed, that try to reach Debian repo, but Debian repo is only reachable over ipv4 (no upstream for ipv6) Disable ipv6 and try again or reboot your ISP/Network/DHCP If you dont get an correct ipv4
saavagebueno commented 2025-11-20 05:14:24 -05:00
Author
Owner
Copy Link

@vicentecandido commented on GitHub (Aug 8, 2025):

Thanks to the community's suggestion to disable IPv6, I was able to resolve the issue by applying the following changes in my OPNsense configuration:

System > Settings > General:

  • Enabled: Prefer to use IPv4 even if IPv6 is available ✅

Interfaces > Settings:

  • Unchecked: Allow IPv6

Interfaces > [WAN]:

  • Set IPv6 Configuration Type to None

The Homarr installation script ran successfully after applying these settings.

Your help was invaluable in getting this resolved. If anyone encounters a similar issue, I hope these steps can help.

@vicentecandido commented on GitHub (Aug 8, 2025): Thanks to the community's suggestion to disable IPv6, I was able to resolve the issue by applying the following changes in my OPNsense configuration: **System > Settings > General:** - Enabled: Prefer to use IPv4 even if IPv6 is available ✅ **Interfaces > Settings:** - Unchecked: Allow IPv6 **Interfaces > [WAN]:** - Set IPv6 Configuration Type to None The Homarr installation script ran successfully after applying these settings. Your help was invaluable in getting this resolved. If anyone encounters a similar issue, I hope these steps can help.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1660
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?