Hellmo_Luciferrari

You can still use PiHole as your DNS when not home if you setup a VPN. For me that was the route I went.

That worked, thank you!

I don't know what I was expecting, but a CAP file wasn't it. I thought it would have just been a BIN file of sorts. Though, I guess now that I think about it, it has been a while since I have done BIOS updates in any other way than through an executable running some sort of flasher mechanism.

Thanks!

Looks like for my mobo they offer an exe, but also a CAP file, which may be a bios update file, who knows. More research needed I suppose.

However, I am at least on the latest as of now since it was back in May that my bios last had an update, and I only switched in the past month.

I haven't investigated updating via USB for my bios. But that likely is the least fuss way to do it.

I will likely have to do some tinkering, and more reading up on this from the documentation I am thinking. I am getting HTTP 200 statuses basically across the board. When going to the FQDN it doesn't redirect to the PiHole admin page like I was expecting. Again, likely some configuration that I have wrong.

Begrudgingly 2 of the 3 are Google email addresses, and 1 is a Microsoft email address. I will however be ditching both of those providers for something a bit more privacy focused soon and making those addresses burner addresses.

Shows in traefik, no errors there.

I hate to report back, but something isn't quite working for pihole behind Traefik.

running "docker logs traefik" returns no error, and yet no certificate was presented to my pihole.

Not sure what else I might be missing or that I might have wrong.

I will give this a shot! Thank you for the help. I will report back, in hopes that between your knowledge and my fumbles that someone else too can learn from this!

so in my traefik.yml file I have cloudflare set as my certresolver as follows:

certificatesResolvers:
  cloudflare:
    acme:
      email: email@example.com
      storage: acme.json
      caServer: https://acme-v02.api.letsencrypt.org/directory # prod (default)
      # caServer: https://acme-staging-v02.api.letsencrypt.org/directory # staging
      dnsChallenge:
        provider: cloudflare
        #disablePropagationCheck: true # uncomment this if you have issues pulling certificates through cloudflare, By setting this flag to true disables the need to wait for the propagation of the TXT record to all aut>
        #delayBeforeCheck: 60s # uncomment along with disablePropagationCheck if needed to ensure the TXT record is ready before verification is attempted 
        resolvers:
          - "1.1.1.1:53"
          - "1.0.0.1:53"

And I had to get the secret mounted via the docker-compose file.

So where you have:

tls:

        certResolver: examplecom-dns

Do I have to redefine all of the same information I did in my Traefik yml but in this separate config.yml?

(I did set it up in my traefik.yml and docker-compose.yml to mount and use this config, which I had commented out for later use.

Thank you so much for the help!

Edit:

Essentially I am trying to get my PiHole which is hosted on another pi setup with an SSL cert for local use only:

So in looking at your config I tried using:

http:
  routers:
    pihole-rtr:
      entryPoints:
      - https
      service: pihole-rtr
      rule: "Host(`ph.local.domain.com`)"
      tls:
        certResolver: cloudflare

  services:
    pihole-svc:
      loadBalancer:
        servers:
          - url: "http://<ip>/admin"

However when doing this error logs returned:

2024-07-08T15:04:27-04:00 ERR error="the service \"pihole-rtr@file\" does not exist" entryPointName=https routerName=pihole-rtr@file
2024-07-08T15:04:28-04:00 ERR error="the service \"pihole-rtr@file\" does not exist" entryPointName=https routerName=pihole-rtr@file

I am doing something very wrong... And feel a little lost.

Would the file provider configs live on the Traefik server, or would they need to be on the external service. Reading through this, and looking at the example configuration files doesn't really seem to point that out. Sorry for the noob questions.

Trying to understand this, but the way the documentation is written is different than I am used to.

Thank you!