3 Proxmox nodes 2 SFF Dell Optiplex (i5 with 32gb RAM) 1 Nuc (i7 with 64gb RAM)

1 Truenas host (old gaming PC i5 with 64gb RAM and 8TB ZFS pool

pfSense appliance for firewall

• Pi-Hole
• Vaultwarden
• Immich
• Paperless-ngx
• InfluxDB + Grafana
• Ansible
• Nextcloud
• Wireguard
• UptimeKuma
• Homeassiatant
• Homepage
• Octoprint

I can agree with everyone here, self hosting mail at this point is pointless. You are going to spend so much of your time reaching out to be pulled off of blacklists only to be added right back onto another. It’s a vicious cycle unfortunately, and than just wait until you get added to Barracudas or Proofpoints naughty list… you may as well start over at that point.

Exactly this! I’m funneling stats from all 3 of my Proxmox nodes. Running VMs, running LXC containers, disk usage, disk latency, network usage, etc. Any stat you can think of monitoring is offered up via the Proxmox API

Im not sure, I am also running Homepage in a docker container, I am able to connect to my pi-hole just fine. From the information I have, it seems like a networking issue.

Its been a long time coming, and is never officially finished. I have most of the host updates automated with Ansible and runs weekly without my attention. Only really need to intervene when something is not working the way it should, or when my automatic updates breaks something…

Im undecided, to be totally candid I am not super confident in my Ansible skills yet, and dont want to push some of my ansible to github and accidentally expose passwords, public IP addresses, etc. I chose Gitea because it was the first application that came up on Google when I googled “self hosted github”…

I am working on vaulting all of that stuff now and will eventually just move over to Github

Never knew about this! Will definitely be checking this out, expect an updated Dashboard in the near future with this widget functioning!

Hey! IM going to post my config below, excuse the formatting if it comes out really messed up, im totally unsure how Lemmy is going to handle this.

- Pihole:
    icon: pi-hole.png # This is the icon that will be displayed on the widget
    href: Link to your PiHole login # Optional, but makes the widget clickable
    description: DNS Server/Ad-Blocker # Description of the service
    ping: IP_ADDRESS_PIHOLE # Options, but will ping the host and display latency
    widget:
        type: pihole # This is required by Homepage to define the type of widget 
        url: http://IP_ADDRESS_PIHOLE
        key: REDACTED # This is an API key generated on the PiHole

Here is the link I used for obtaining the API key. https://pi-hole.net/blog/2022/11/17/upcoming-changes-authentication-for-more-api-endpoints-required/#page-content

Let me know if you have any issues!

Awesome, that’s great to hear! Glad I could provide some inspiration

No problem! I used Heimdall for a while too, until someone recommended Homepage. Never looked back! The API support for certain applications really drives it home for me.

Its called Homepage. Link here! https://github.com/benphelps/homepage

Really easy to set up and even easier to configure, its just a few yml files that need to be modified to add new entries to the dashboard. They have some great documentation too!