Differences

This shows you the differences between two versions of the page.

--- installing_pi_hole_linux_ubuntu_version_24_04 [2026/08/17 20:07] – wikiadmin
+++ installing_pi_hole_linux_ubuntu_version_24_04 [2026/08/17 21:05] (current) – wikiadmin
@@ Line 145: / Line 145: @@
 </code>
+<code>
+  [\e[1;31m✗\e[0m] Failed to set dns.queryLogging. Try with sudo power
+root@xcsvr:/etc/systemd# 0;53;27m
+: command not found
+: command not found
+m: command not found
+</code>
+Force Pi-hole v6 to immediately use port 8080 via the official Command Line Interface (CLI) tool:
+Run this terminal command on your 192.168.1.152 server:
+<code>
+sudo pihole-FTL --config webserver.port "8080o,443os,[::]:8080o,[::]:443os"
+</code>
+Use code with caution.
+Restart the core engine to force-bind the new ports:
+<code>
+sudo systemctl restart pihole-FTL
+</code>
+Check status and Open the Uncomplicated firewall port 8080 if necessary
+<code>
+sudo ufw status
+sudo ufw open 8080/tcp
+</code>
+Here is exactly how to configure Pi-hole and Apache to make this work.
+Step 1: Add Local DNS Records in Pi-hole.
+You must tell Pi-hole to intercept the public domains and resolve them to your internal server IPs instead of the public WAN IP.
+Log into your Pi-hole admin dashboard (http://192.168.1.152:8080/admin).
+Navigate to Local DNS > DNS Records on the sidebar.
+Add the following three records:
+Domain IP Address Description
+<code>
+sunsky.cloud 192.168.1.152  Points Nextcloud to the Apache server
+onlyoffice.sunsky.cloud 192.168.1.152 Points 1st OnlyOffice to the Apache server
+officepkg.com 192.168.1.152 Crucial: Points to Apache first, not .156
+</code>
+Note on officepkg.com: Because Apache handles your Let's Encrypt SSL certificates on 192.168.1.152, local traffic must hit Apache first so it can terminate the SSL connection before proxying the traffic to the second server (192.168.1.156).