Proxmox Server

How are you managing adguard1 and adguard2 at the client / router level? DO you give out both IPs or does adguard have some load balancing feature
I have both Adguard addresses added to the DHCP settings that my Mikrotik hands out.

It seems to use round-robin, not failover, although you could do failover with some mangle rules and DNS interception/redirection
 
Just finished some maintenance:
  • Fixed my dodgy multi-Pihole setup - but need to keep monitoring it as my FTL service keeps crashing because of a port 53 conflict
  • Setup Wake on LAN for my devices - so if anything happens I can remotely restart my nodes

Edit: also started documenting the stuff - better late than never
 
Last edited:
Just finished some maintenance:
  • Fixed my dodgy multi-Pihole setup - but need to keep monitoring it as my FTL service keeps crashing because of a port 53 conflict
  • Setup Wake on LAN for my devices - so if anything happens I can remotely restart my nodes

Edit: also started documenting the stuff - better late than never
Have you looked into Ansible, to make stuff automated/documented? Always hard to go back a few months and think which script/hack/modification you used to get xyz to work the way it should.

Regarding the port 53 conflict, I had the same issue and had to use netstat to try figure out what was causing the port to not be bound. In the end I got extremely irritated and just loaded it as an LXC with its own IP address, and it has been fine since.

WOL is nice; now all you need is a JetKVM to be fully sorted. I am also keeping my eye on the Openterface Lite KVM which looks like an interesting product for those of us who don't have Intel vPro/AMD Dash/Dell iDRAC/HP iLO available.
 
Have you looked into Ansible, to make stuff automated/documented? Always hard to go back a few months and think which script/hack/modification you used to get xyz to work the way it should.

Regarding the port 53 conflict, I had the same issue and had to use netstat to try figure out what was causing the port to not be bound. In the end I got extremely irritated and just loaded it as an LXC with its own IP address, and it has been fine since.

WOL is nice; now all you need is a JetKVM to be fully sorted. I am also keeping my eye on the Openterface Lite KVM which looks like an interesting product for those of us who don't have Intel vPro/AMD Dash/Dell iDRAC/HP iLO available.
So ive seen other people using Ansible and never thought it would be applicable to me but perhaps this is something i need to look at as part of the documentation - for now im just just using an Obsidian file + Draw.IO

My port 53 issue was caused by my incorrectly configured Nebula Sync container - i fixed this and my Piholes have been behaving since - so the problem was a pebkac. So interestingly with WOL i got it to work on the machine you sent me plus the other HP SFF device but my 3rd HP machine is working - same config etc - must be something in the BIOS which is where something like JetKVM would come in and be useful - all this money and time being posted into the homelab ventures
 
Easiest would be a BIOS update then reset it to defaults, and try again to see if you can get WOL to work. Did you manage to figure out AMD Dash yet?

Homelabbing is my cheapest hobby yet - most rewarding, and also has usecases that benefits my whole family.

Now, cycling, on the other hand...that is a deep hole to go down (and a nearly endless one in terms of what money you can spend).
 
Proxmox Virtual Environment 9 released

 
Proxmox Virtual Environment 9 released


Just did my upgrade via ssh and went smoothly. Nothing major running on it but worked out okay.
 
And all done. Both nodes are now on 9.0.3.

Zero issues encountered, and it took around 15 minutes per node, the limitation being my slow-ish internet as the package files are around 700mb in size.
 
And all done. Both nodes are now on 9.0.3.

Zero issues encountered, and it took around 15 minutes per node, the limitation being my slow-ish internet as the package files are around 700mb in size.

It was also slow for me. I think its the server because I did it on my server hosted at the data centre with a 1G dedicated unmetered link and it was pulling at 250KB/s max during the update.
 
It was also slow for me. I think its the server because I did it on my server hosted at the data centre with a 1G dedicated unmetered link and it was pulling at 250KB/s max during the update.
Hmmm, that is bizarre. Mine was not that slow, but I have a rather meagre 30/30 link here at home, but it was running close to line speed.

The new resource graphs are pretty nice - having the disk IO, memory pressure stall, CPU pressure stall and IO pressure stall figures helps to see what is eating up valueable resources.

It also looks like you can export data to Grafana, InfluxDB and OpenTelemetry as well. Definitely going to dive into this soon.
 
Peer pressure got to me and managed to update all 3 - 1 had a warning about space so had to cleanup some old packages but went great after
 
Anyone have random VM reboots of guests running on their Proxmox hosts?

There is nothing in the Proxmox VE logs so it looks like a VM failure. But I am certain it’s something in particular with my setup as it happens across both my nodes (identical machines, Optiplex Thin Client 3000’s), and moving the VM from one node to another yields no difference.

Nothing in the VM logs either, which is making troubleshooting harder than it should be.
 
Anyone have random VM reboots of guests running on their Proxmox hosts?

There is nothing in the Proxmox VE logs so it looks like a VM failure. But I am certain it’s something in particular with my setup as it happens across both my nodes (identical machines, Optiplex Thin Client 3000’s), and moving the VM from one node to another yields no difference.

Nothing in the VM logs either, which is making troubleshooting harder than it should be.
Haven't seen anything on my end - could it be resource exhaustion? Memory leaks?
 
Haven't seen anything on my end - could it be resource exhaustion? Memory leaks?
Resources seem good, I even moved the one crashing VM to my other node and the issue persists. So I doubt that it's tied to hardware, but maybe it's something misconfigured on my end when setting up the VM.

When I have a moment I will do some more digging.
 
hopefully its not a critical VM
Resources seem good, I even moved the one crashing VM to my other node and the issue persists. So I doubt that it's tied to hardware, but maybe it's something misconfigured on my end when setting up the VM.

When I have a moment I will do some more digging.
 
Top
Sign up to the MyBroadband newsletter
X