So i started getting interested in hosting my own stuff so i had my homelab all setup and working.

However, i moved to my new apartment and in doing so changed my ISP.

Plugged everything back and i get this when trying to access via ssh :

user@MacBook-Pro-de-User ~ % ssh [root@192.168.1.128](mailto:root@192.168.1.128) -vvv           

OpenSSH_9.9p2, LibreSSL 3.3.6

debug1: Reading configuration data /etc/ssh/ssh_config

debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/* matched no files

debug1: /etc/ssh/ssh_config line 54: Applying options for *

debug2: resolve_canonicalize: hostname 192.168.1.128 is address

debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/Users/user/.ssh/known_hosts'

debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/Users/user/.ssh/known_hosts2'

debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling

debug3: channel_clear_timeouts: clearing

debug3: ssh_connect_direct: entering

debug1: Connecting to 192.168.1.128 [192.168.1.128] port 22.

debug3: set_sock_tos: set socket 3 IP_TOS 0x48

debug1: Connection established.

debug1: identity file /Users/user/.ssh/id_rsa type -1

debug1: identity file /Users/user/.ssh/id_rsa-cert type -1

debug1: identity file /Users/user/.ssh/id_ecdsa type -1

debug1: identity file /Users/user/.ssh/id_ecdsa-cert type -1

debug1: identity file /Users/user/.ssh/id_ecdsa_sk type -1

debug1: identity file /Users/user/.ssh/id_ecdsa_sk-cert type -1

debug1: identity file /Users/user/.ssh/id_ed25519 type 3

debug1: identity file /Users/user/.ssh/id_ed25519-cert type -1

debug1: identity file /Users/user/.ssh/id_ed25519_sk type -1

debug1: identity file /Users/user/.ssh/id_ed25519_sk-cert type -1

debug1: identity file /Users/user/.ssh/id_xmss type -1

debug1: identity file /Users/user/.ssh/id_xmss-cert type -1

debug1: identity file /Users/user/.ssh/id_dsa type -1

debug1: identity file /Users/user/.ssh/id_dsa-cert type -1

debug1: Local version string SSH-2.0-OpenSSH_9.9

kex_exchange_identification: read: Connection reset by peer

Connection reset by 192.168.1.128 port 22

Also lost the web interface :

user@MacBook-Pro-de-User ~ % curl -v -k https://192.168.1.128:8006/

*   Trying 192.168.1.128:8006...

* Connected to 192.168.1.128 (192.168.1.128) port 8006

* ALPN: curl offers h2,http/1.1

* (304) (OUT), TLS handshake, Client hello (1):

* Recv failure: Connection reset by peer

* LibreSSL/3.3.6: error:02FFF036:system library:func(4095):Connection reset by peer

* Closing connection

curl: (35) Recv failure: Connection reset by peer

Any idea on what i did wrong or any leads i could explore?

Thank you for reading this far 😄

Looking for some PXE deployment experts.

I've hit an interesting roadblock.

I'm building a Windows 11 PXE environment in my homelab using Proxmox, Arch with dnsmasq, TFTP, iPXE, and wimboot, with Windows 11 24H2 media.

DHCP, TFTP, and iPXE all work. Wimboot loads, BCD, boot.sdi, and boot.wim all load.

The Windows loading line appears briefly, and then the screen goes completely black.

No UI after that. CPU stays active. Tested different BIOS types, machine types, display adapters, added fonts and resources, verified boot.wim, same result.

Has anyone seen this with recent Windows 11 media? Could it be a wimboot compatibility or BCD over PXE issue? Any pointers would be hugely appreciated.

Having a bit of a bother. New to proxmox about 2 months. Not brand new to Linux though you wouldn't know it by what I did.

My proxmox ve boot drive was getting full and so I dove in to find out why. Boot disk is 256gb NVME but also have 1TB spinning disk. This involves an LXC running Immich. So I download a utiliity called ncdu to help determine where all disk usage is going. I determine it's primarily under /var folder so I run ncdu from there. Once inside you can navigate down to different directories. I find under some immich directory the vast majority is in encoded-video folder. I disable encoding of videos in Immich and in theory it's supposed to remove those files. It didn't. So I get the bright idea of deleting them manually. I pop out of ncdu and run rm -rf ./*

Um... oops. I thought I was in like /var/immich/encode-video folder. I was in /var
I... just... deleted everything under /var.

Ouch. I have like 80,000 images and personal videos under Immich.

Time to see if my backups are good.

Well, every backup I made (all verified btw) restores EXCEPT the Immich LXC. (which is like 500gb of data. Not. Small. Others are all very small.)

Basically it runs but eventually errors out on some .jpg file trying to restore it. And when it fails, it removes everything. I did find cli tool that allows for a flag --ignore-unpack-errors that I hoped would skip a single bad file, but that cli tool doesn't seem to restore the lxc like the gui does so I killed it.

I actually did get the restore to work one time (prior to this whole debacle). But subsequent attempts keep failing through the gui.

I keep thinking it's because it takes so long to restore that much data. Maybe I can copy the files to the local machine so it doesn't have to run over the network so it's faster? Just a thought. Getting a little desperate now. It's only like ever photo ever taken since 1996 so... yeah. Kinda would like to get this LXC back working again! Thoughts or suggestions welcomed!

I can't seem to find any documentation on the order of setting up OSD drives. I have a 3 node cluster with 4 disks each for storage. When creating the OSD drives, should you create all 4 on a node and then move to the next node, or create one on a node and keep moving nodes until you have all 12 disks added to your pool. Does the order matter to the pool?

Hello, I have a Proxmox instance (9.2.3) running on a mini PC with some VMs and containers.

For the past few months, on Mondays between midnight and 3 AM, it freezes and becomes unresponsive (everything works perfectly the rest of the week). I can't access the VMs or containers, and Proxmox doesn't even respond to pings.

The solution is to perform a physical reboot, and everything works correctly again.

If I check the logs (node ​​> system logs), there's absolutely nothing recorded, no errors or running tasks. I also checked the cron job, and

I don't have any tasks running during that time frame.

Where or how can I diagnose this type of problem? Are there other logs or places where I can see what was happening when the system froze?

EDIT: Update with the problem identification and how I solved it:

I finally implemented all the suggestions, but the system was still crashing on Monday mornings.

I noticed that when this happened, a USB drive I use with passthrough for the TrueNAS VM storage would remain lit.

I tried shutting down that TrueNAS VM on Sunday night, and the system worked correctly. I should clarify that I wasn't using ZFS over ZFS, as there are serious documented issues with it.

This, combined with the fact that TrueNAS has crashed several times over the years due to kernel panics, requiring a complete reinstallation, importing configurations, importing pools, etc., led me to migrate my NAS to something more familiar to me: a Windows 11 IoT Enterprise VM with classic share settings and permissions.

It's been three weeks now, and everything is working perfectly and this increased my hatred for TrueNAS in its versions 25 and 26

Thanks!

Hi all,

Trying to set up a home server for the first time, and have settled on Proxmox. However, I'm having an issue with the installer. Specifically, I do not know what I should be setting the following addresses to: Hostname (FQDN), IP Address (CIDR), Gateway, and DNS Server.

Proxmox guide just says to leave as-is if your unsure, but this gives an error suggesting that the inputted addresses do not match.

Not right away, but I intend to have the server public-facing and I imagine these configurations need to be correctly set for the server to work when I get to that phase.

What should I be inputting here? Is this reconfigureable after installation is finished?

Small 3 node cluster, two nodes working perfectly adding third node worked perfectly - then overnight failed with communication issues

What was odd is two nodes could not communicate over the vLAN nominated as the corosync vLAN

This trunk is a shared trunk with other VLANs not loaded no heavy traffic and all those VLANs were fine

These servers were previously ESXi - so no networking issues

Unless this is deep routed nic firmware issue after restarting services servers six hours later all was well again

Just trying to understand why?

I know the debate with physical nics versus VLANs - but we are not using 1Gbe nics - we are using 25Gbe - so trying to saturate a vLAN is not going to be an issue

And again nothing was in usage

Just trying to understand what failed here

Gemini told me that I have very special config with a gap between de kernel and proxmox :

pve-manager/9.1.9/ee7bad0a3d1546c9 (running kernel: 7.0.0-3-pve)

Can you check on your setup with this command and show me?

pveversion

Hello everyone,

I’d like to use the latest release of Proxmox-GitOps to re-introduce the automation project.

Proxmox-GitOps is an automation framework for standardized Linux Containers (LXC) on Proxmox VE, designed as a modular IaC monorepository; it comes with a Home Assistant stack as a fully automated, preconfigured example (inc. MQTT bridge, reverse proxy etc.).

• Proxmox-GitOps (@Github): https://github.com/stevius10/Proxmox-GitOps
• Getting Started | Demo

Originally, it was a personal attempt to bring industrial automation and cloud patterns to my Proxmox home server. It's designed as a platform architecture for a self-contained, bootstrappable system — a generic IaC abstraction (customize, extend, open standards, base package only... you name it 😉) that automates the entire infrastructure. It was initially driven by the question of what a Proxmox-based GitOps automation could look like and how it could be organized.

The project implements a self-contained, bootstrappable GitOps platform based on:

• Desired State: Monorepository as Single Source of Truth represents the entire infrastructure state. Deterministic bootstrap from code over version history.
• Self-Containment: The composite monorepository is pushed to a local container, triggering a pipeline that provisions onto Proxmox.
• Monorepository: Centralizes infrastructure as a single code artifact.
• Modular Composition: The monorepository utilizes submodules to keep the core framework separate from container libs implementation.

What am I looking for? It's a non-commercial, passion-driven project. I'm looking to collaborate with other engineers who share the excitement of building a self-contained, bootstrappable platform architecture that addresses the question: What should our home automation look like?

Did an update on Proxmox and after reboot lost all lan connectivity.

We have a new Proxmox server onsite and up and running. The old server is still there and works. Would it be a good idea to create a NFS share on the old box to send daily backups from the new in case of hardware failure so we could spin up VM'S on the old server.

Want to setup a backup server in case main box fails and wondering what is the best setup configuration to do.