SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-29 09:12:42 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Update does not work in pihole lxc #1863

New Issue
Closed
opened 2025-11-20 05:18:42 -05:00 by saavagebueno · 8 comments
saavagebueno commented 2025-11-20 05:18:42 -05:00
Owner
Copy Link

Originally created by @miguelcastilho on GitHub (Sep 7, 2025).

✅ Have you read and understood the above guidelines?

yes

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

pihole

📂 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

📈 Which Proxmox version are you on?

8.4.12

📝 Provide a clear and concise description of the issue.

pihole lxc does not update when issuing the command update instead I get this error

root@pihole:~# update
curl: (22) The requested URL returned error: 404

Updating with the following command works
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pihole.sh)"

🔄 Steps to reproduce the issue.

install pihole lxc and then execute the update command

❌ Paste the full error output (if available).

root@pihole:~# update
curl: (22) The requested URL returned error: 404

🖼️ Additional context (optional).

No response

Originally created by @miguelcastilho on GitHub (Sep 7, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? pihole ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 8.4.12 ### 📝 Provide a clear and concise description of the issue. pihole lxc does not update when issuing the command `update` instead I get this error ``` root@pihole:~# update curl: (22) The requested URL returned error: 404 ``` Updating with the following command works `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pihole.sh)"` ### 🔄 Steps to reproduce the issue. install pihole lxc and then execute the `update` command ### ❌ Paste the full error output (if available). ``` root@pihole:~# update curl: (22) The requested URL returned error: 404 ``` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the not a script issue label 2025-11-20 05:18:42 -05:00
saavagebueno commented 2025-11-20 05:18:43 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 7, 2025):

404 = your Network Block all calls or call incorrect, there is nothing what we can do. It Blocks the whole curl to our repo

@MickLesk commented on GitHub (Sep 7, 2025): 404 = your Network Block all calls or call incorrect, there is nothing what we can do. It Blocks the whole curl to our repo
saavagebueno commented 2025-11-20 05:18:43 -05:00
Author
Owner
Copy Link

@miguelcastilho commented on GitHub (Sep 7, 2025):

The reason is because the url used by the update command is wrong. after updating the file at /bin/bash/update with the correct url then it works

@miguelcastilho commented on GitHub (Sep 7, 2025): The reason is because the url used by the update command is wrong. after updating the file at `/bin/bash/update` with the correct url then it works
saavagebueno commented 2025-11-20 05:18:43 -05:00
Author
Owner
Copy Link

@miguelcastilho commented on GitHub (Sep 7, 2025):

404 = your Network Block all calls, there is nothing what we can do. It Blocks the whole curl to our repo

also, this comment does not make sense because, as i stated in the description, doing the curl works

@miguelcastilho commented on GitHub (Sep 7, 2025): > 404 = your Network Block all calls, there is nothing what we can do. It Blocks the whole curl to our repo also, this comment does not make sense because, as i stated in the description, doing the curl works
saavagebueno commented 2025-11-20 05:18:43 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 7, 2025):

Allright, Just old or wrong bash call? So can be closed?

@MickLesk commented on GitHub (Sep 7, 2025): Allright, Just old or wrong bash call? So can be closed?
saavagebueno commented 2025-11-20 05:18:44 -05:00
Author
Owner
Copy Link

@miguelcastilho commented on GitHub (Sep 7, 2025):

i just confirmed in a new install it works. the bug is only specific to a old install

@miguelcastilho commented on GitHub (Sep 7, 2025): i just confirmed in a new install it works. the bug is only specific to a old install
saavagebueno commented 2025-11-20 05:18:44 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Sep 7, 2025):

404 = your Network Block all calls, there is nothing what we can do. It Blocks the whole curl to our repo

also, this comment does not make sense because, as i stated in the description, doing the curl works

It makes perfect sense because @MickLesk assumed you have a proper url in the update script. If you get 404 or any such errors running update, only logical conclusion is that there is something on your network thats blocking the call.

Anyway, what was the URL in your install, before you changed it?

@tremor021 commented on GitHub (Sep 7, 2025): > > 404 = your Network Block all calls, there is nothing what we can do. It Blocks the whole curl to our repo > > also, this comment does not make sense because, as i stated in the description, doing the curl works It makes perfect sense because @MickLesk assumed you have a proper url in the update script. If you get 404 or any such errors running update, only logical conclusion is that there is something on your network thats blocking the call. Anyway, what was the URL in your install, before you changed it?
saavagebueno commented 2025-11-20 05:18:44 -05:00
Author
Owner
Copy Link

@miguelcastilho commented on GitHub (Sep 7, 2025):

It’s not correct to say this was a network issue. As I mentioned, running the curl manually works fine, so my network was never blocking access.

The actual problem was that in older installs the update script pointed to an outdated/incorrect URL, which resulted in the 404. After correcting the URL, the update worked immediately.

I tested on a fresh install and confirmed that the latest version already has the proper URL, so the issue only affects older installs.

@miguelcastilho commented on GitHub (Sep 7, 2025): It’s not correct to say this was a network issue. As I mentioned, running the curl manually works fine, so my network was never blocking access. The actual problem was that in older installs the update script pointed to an outdated/incorrect URL, which resulted in the 404. After correcting the URL, the update worked immediately. I tested on a fresh install and confirmed that the latest version already has the proper URL, so the issue only affects older installs.
saavagebueno commented 2025-11-20 05:18:44 -05:00
Author
Owner
Copy Link

@probert94 commented on GitHub (Sep 8, 2025):

I had the same issue for Jellyfin and Nginx Proxy Manager. The issue in both cases was an additional "raw" in the path of the url: https://raw.githubusercontent.com/community-scripts/ProxmoxVE/raw/main/ct/jellyfin.sh
So to fix the issue edit the file /bin/update and remove the /raw

@probert94 commented on GitHub (Sep 8, 2025): I had the same issue for Jellyfin and Nginx Proxy Manager. The issue in both cases was an additional "raw" in the path of the url: https:<span></span>//raw.githubusercontent.com/community-scripts/ProxmoxVE`/raw`/main/ct/jellyfin.sh So to fix the issue edit the file `/bin/update` and remove the `/raw`
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 not a script issue
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#1863
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?