Hi,
Thanks for the help. I was able to get back into system. I installed Pihole and fixed most issues I thought. The DNS is not working in Pihole ? Everything else seems ok but also I cannot get my web gui up ? I am going to play with this more. If you have any idea please let me know ? Rienstall ?
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
Hi,
I was able to get Web interface up.
I just cannot seem to get Ftl and dns server running. It looks like I am having the port 53 and 80 conflicts ? I have tried the fixes but cannot get Ftl to run. DNS is not working either ?
For your own privacy and safety, don't post your unsanitised debug log publically.
We only ask for the token displayed after uploading the log has completed.
Hi,
I upgraded os to Bullseye and install Pihole. I still cannot get Dns server to run?
Here is my Debug token. Any help is appreciated. https://tricorder.pi-hole.net/lMMColu5/
Thanks
Hi,
I have never really tried anything like this but was reading post on repurposing my cloudkey. I have been able to get pretty far by reading post and looking into project. I was told that it was my Os and it was not supported. Was able to upgrade it. It still having with DNS not running. Any help would be appreciated. Ideas or where to start ?
Thanks
Something is bugging setting capabilities via systemd directives on Cloudkey's that have been upgraded to Buster:
About Linux capabilities:
$ man capabilities
[..]
CAPABILITIES(7) Linux Programmer's Manual CAPABILITIES(7)
NAME
capabilities - overview of Linux capabilities
DESCRIPTION
For the purpose of performing permission checks, traditional
UNIX implementations distinguish two categories of processes:
privileged processes (whose effective user ID is 0, referred
to as superuser or root), and unprivileged processes (whose
effective UID is nonzero). Privileged processes bypass all
kernel permission checks, while unprivileged processes are
subject to full permission checking based on the process's
credentials (usually: effective UID, effective GID, and sup‐
plementary group list).
Starting with kernel 2.2, Linux divides the privileges tradi‐
tionally associated with superuser into distinct units, known
as capabilities, which can be independently enabled and dis‐
abled. Capabilities are a per-thread attribute.
Capabilities list
The following list shows the capabilities implemented on
Linux, and the operations or behaviors that each capability
permits:
CAP_AUDIT_CONTROL (since Linux 2.6.11)
Enable and disable kernel auditing; change auditing
filter rules; retrieve auditing status and filtering
rules.
[..]
Hi,
My Cloudkey is not giving me access and will not reset. I am going to try to get into it using a Direct Pc ethernet connection. Thanks for your help. I was not able to try your steps yet. I was updating apt a tried Upgrade to Maintainers version. I will update.