Traefik proxy primarily for internal use (unable to connect Proxmox webGUI)

Traefik Traefik v2 (latest)
1

My use of Traefik is to use on my local network for testing purposes prior to also exposing it to the cloud. Specifically my use case is to use with Proxmox and the several KVMs and LXCs, not with application containerisation (e.g. Docker, Kubernetes, etc).

I have installed Traefik-proxy 2.9.4 in its own Proxmox LXC (have tried both privileged and unprivileged) using the standalone package in a Debian 11 environment. I can access the Traefik dashboard and all file rules work in real-time with no issues.

Unfortunately I have been unable to setup Traefik to access the webGUI of Proxmox VE, although I believe I have used the right settings. What is it I am missing. I use Pi-hole for DNS and .local as the domain name for all internal servers. Pi-hole does not forward .local DNS queries to the cloud. My Proxmox VE server can be nslookup/pinged with both the IP address (192.168.1.234) and hostname (pve.local).

My traefik.yml file:

providers:
 file:
   directory: "/user/traefik-config"
   watch: true
api:
   dashboard: true
   insecure: true
entryPoints:
 web:
   address: ":80"
 websecure:
   address: ":443"
#required for Proxmox discovery
serversTransport:
 insecureSkipVerify: true

My proxmox-pve.yml file:

http:
  routers:
    proxmox-https:
      rule: "Host(`pve.local`)"
      service: proxmox-service
      entrypoints:
        - websecure
      tls: {}

  services:
    proxmox-service:
      loadBalancer:
        servers:
          - url: "https://192.168.1.234:8006"

What is it I am missing to be able to see the Proxmox webGUI using Traefik-proxy.

2

Problem solved. I was using the wrong IP address in the Pi-hole. For anyone reading this in the future the above simple config files will correctly allow Traefik-proxy to connect to Proxmox VE webGUI.

If you are using Pi-hole or any other local DNS server you have to add/associate the hostname (in my case pve.local) with the IP address of the traefik server (in my case 192.168.1.123).

Using the above logic you can add any Proxmox KVM/LXC to be handled by Traefik-proxy.