Wrong SSH key being presented by new containers

petersrin

New Member
Dec 14, 2024
2
1
1
  1. Spin up a new Debian 12 LXC
  2. Windows Client:
    Code:
    ssh [ip]
  3. I'm presented with a fingerprint using ed25519
  4. Proxmox > LXC > Shell:
    Code:
    ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key
  5. I'm presented with a DIFFERENT fingerprint than the one showing up on my client
Previous containers I've installed show the same host fingerprint, but suddenly that behavior has changed. I feel like I'm missing something super obvious. This is all on a local network and there's literally no one on my premesis for an acre, so it's very not likely to be a MITM, but I'm absolutely scratching my head on this.

This is also relevant because I can't SSH into the container. I have:
  1. Enabled root by password (for now just for the simplest test)
  2. Rebooted the container
  3. Cleared my client ssh config completely
  4. Emptied out my client SSH Agent with
    Code:
    ssh-add -d
  5. Code:
    apt update && apt upgrade
    on both proxmox and container
I can still get into my other containers from the client.
 
Ugh. Never mind, y'all. [SOLVED]. It was a rogue IP reservation on my router which kept pointing to the wrong server. That's embarassing, but at least my initial assumption: operator error, was right!
 
  • Like
Reactions: fba

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!