starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Pi-Hole installation ends in error #541

New Issue
Closed
opened 2026-02-04 19:43:40 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-04 19:43:40 +03:00
Owner
Copy Link

Originally created by @philipmae on GitHub (Feb 23, 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?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/pihole.sh)"

📝 Provide a clear and concise description of the issue.

LXC is created but ends in error while trying to install pihole.

[ERROR] in line 27: exit code 0: while executing command $STD bash <(curl -fsSL https://install.pi-hole.net) --unattended

Down below I will attach the last few lines of the full log

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Step 1: paste install script command
Step 2: Select default settings with verbose output

❌ Paste the full error output (if available).

` ✔️ Installed Dependencies
⠹ Installing Pi-hole
[✓] Root user check

    .;;,.
    .ccccc:,.
     :cccclll:.      ..,,
      :ccccclll.   ;ooodc
       'ccll:;ll .oooodc
         .;cll.;;looo:.
             .. ','.
            .',,,,,,'.
          .',,,,,,,,,,.
        .',,,,,,,,,,,,....
      ....''',,,,,,,'.......
    .........  ....  .........
    ..........      ..........
    ..........      ..........
    .........  ....  .........
      ........,,,,,,,'......
        ....',,,,,,,,,,,,.
           .',,,,,,,,,'.
            .',,,,,,'.
              ..'''.

[i] SELinux not detected
[✓] Update local cache of available packages

[✗] Checking apt-get for upgraded packages
Kernel update detected. If the install fails, please reboot and try again
[✓] Building dependency package pihole-meta.deb
[✓] Installing Pi-hole dependency package

⠏ [✗] Retrieval of supported OS list failed. dig failed with return code 10.
Unable to determine if the detected OS (Debian 12) is supported
Possible causes for this include:
- Firewall blocking DNS lookups from Pi-hole device to ns1.pi-hole.net
- DNS resolution issues of the host system
- Other internet connectivity issues

  https://docs.pi-hole.net/main/prerequisites/#supported-operating-systems

  If you wish to attempt to continue anyway, you can try one of the following commands to skip this check:

  e.g: If you are seeing this message on a fresh install, you can run:
         curl -sSL https://install.pi-hole.net | sudo PIHOLE_SKIP_OS_CHECK=true bash

       If you are seeing this message after having run pihole -up:
         sudo PIHOLE_SKIP_OS_CHECK=true pihole -r
       (In this case, your previous run of pihole -up will have already updated the local repository)

  It is possible that the installation will still fail at this stage due to an unsupported configuration.
  If that is the case, you can feel free to ask the community on Discourse with the Community Help category:
  https://discourse.pi-hole.net/c/bugs-problems-issues/community-help/

⠋
[ERROR] in line 27: exit code 0: while executing command $STD bash <(curl -fsSL https://install.pi-hole.net) --unattended`

🖼️ Additional context (optional).

No response

Originally created by @philipmae on GitHub (Feb 23, 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? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/pihole.sh)" ### 📝 Provide a clear and concise description of the issue. LXC is created but ends in error while trying to install pihole. `[ERROR] in line 27: exit code 0: while executing command $STD bash <(curl -fsSL https://install.pi-hole.net) --unattended` Down below I will attach the last few lines of the full log ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Step 1: paste install script command Step 2: Select default settings with verbose output ### ❌ Paste the full error output (if available). ` ✔️ Installed Dependencies ⠹ Installing Pi-hole [✓] Root user check .;;,. .ccccc:,. :cccclll:. ..,, :ccccclll. ;ooodc 'ccll:;ll .oooodc .;cll.;;looo:. .. ','. .',,,,,,'. .',,,,,,,,,,. .',,,,,,,,,,,,.... ....''',,,,,,,'....... ......... .... ......... .......... .......... .......... .......... ......... .... ......... ........,,,,,,,'...... ....',,,,,,,,,,,,. .',,,,,,,,,'. .',,,,,,'. ..'''. [i] SELinux not detected [✓] Update local cache of available packages [✗] Checking apt-get for upgraded packages Kernel update detected. If the install fails, please reboot and try again [✓] Building dependency package pihole-meta.deb [✓] Installing Pi-hole dependency package ⠏ [✗] Retrieval of supported OS list failed. dig failed with return code 10. Unable to determine if the detected OS (Debian 12) is supported Possible causes for this include: - Firewall blocking DNS lookups from Pi-hole device to ns1.pi-hole.net - DNS resolution issues of the host system - Other internet connectivity issues https://docs.pi-hole.net/main/prerequisites/#supported-operating-systems If you wish to attempt to continue anyway, you can try one of the following commands to skip this check: e.g: If you are seeing this message on a fresh install, you can run: curl -sSL https://install.pi-hole.net | sudo PIHOLE_SKIP_OS_CHECK=true bash If you are seeing this message after having run pihole -up: sudo PIHOLE_SKIP_OS_CHECK=true pihole -r (In this case, your previous run of pihole -up will have already updated the local repository) It is possible that the installation will still fail at this stage due to an unsupported configuration. If that is the case, you can feel free to ask the community on Discourse with the Community Help category: https://discourse.pi-hole.net/c/bugs-problems-issues/community-help/ ⠋ [ERROR] in line 27: exit code 0: while executing command $STD bash <(curl -fsSL https://install.pi-hole.net) --unattended` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the not a script issue label 2026-02-04 19:43:40 +03:00
OVERLORD commented 2026-02-04 19:43:57 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 23, 2025):

As Default? Cant reproduce this.

@MickLesk commented on GitHub (Feb 23, 2025): As Default? Cant reproduce this.
OVERLORD commented 2026-02-04 19:44:03 +03:00
Author
Owner
Copy Link

@philipmae commented on GitHub (Feb 23, 2025):

Yes default with verbose output. Let me know what additional information you need.

@philipmae commented on GitHub (Feb 23, 2025): Yes default with verbose output. Let me know what additional information you need.
OVERLORD commented 2026-02-04 19:44:08 +03:00
Author
Owner
Copy Link

@bvdberg01 commented on GitHub (Feb 23, 2025):

For me, the script works fine in default mode with verbose enabled.
Did you check the verbose output for possible causes? In particular this part:

Possible causes for this include:
- Firewall blocking DNS lookups from Pi-hole device to ns1.pi-hole.net
- DNS resolution issues of the host system
- Other internet connectivity issues
@bvdberg01 commented on GitHub (Feb 23, 2025): For me, the script works fine in default mode with verbose enabled. Did you check the verbose output for possible causes? In particular this part: ``` Possible causes for this include: - Firewall blocking DNS lookups from Pi-hole device to ns1.pi-hole.net - DNS resolution issues of the host system - Other internet connectivity issues ```
OVERLORD commented 2026-02-04 19:44:17 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Feb 24, 2025):

This is a issue with your DNS, not the script.

⠏ [✗] Retrieval of supported OS list failed. dig failed with return code 10.
Unable to determine if the detected OS (Debian 12) is supported
Possible causes for this include:
- Firewall blocking DNS lookups from Pi-hole device to ns1.pi-hole.net
- DNS resolution issues of the host system
- Other internet connectivity issues
@michelroegl-brunner commented on GitHub (Feb 24, 2025): This is a issue with your DNS, not the script. ``` ⠏ [✗] Retrieval of supported OS list failed. dig failed with return code 10. Unable to determine if the detected OS (Debian 12) is supported Possible causes for this include: - Firewall blocking DNS lookups from Pi-hole device to ns1.pi-hole.net - DNS resolution issues of the host system - Other internet connectivity issues ```
OVERLORD commented 2026-02-04 19:44:23 +03:00
Author
Owner
Copy Link

@iLLNESS commented on GitHub (Mar 2, 2025):

I get the same issue. I can ping ns1.pi-hole.net just fine in the LXC but get the error regardless.

Using the command PIHOLE_SKIP_OS_CHECK=true pihole -r works but something seems to be broken in v6 pihole on this LXC.

In my case it seems that the LXC is trying to use an external DNS for this task regardless of what DNS server I had set which my firewall was blocking. Not sure why this LXC is trying to bypass the DNS settings set in the LXC. It did not used to do that.

@iLLNESS commented on GitHub (Mar 2, 2025): I get the same issue. I can ping ns1.pi-hole.net just fine in the LXC but get the error regardless. Using the command PIHOLE_SKIP_OS_CHECK=true pihole -r works but something seems to be broken in v6 pihole on this LXC. In my case it seems that the LXC is trying to use an external DNS for this task regardless of what DNS server I had set which my firewall was blocking. Not sure why this LXC is trying to bypass the DNS settings set in the LXC. It did not used to do that.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#541
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?