Installed Proxmox on top of Debian, locked out.

B

baugen

New Member
Feb 3, 2025
1
0
1
So I have a remote test rig that i have been running Debian on, just testing some different setups. The only thing installed was Debian 12 with Docker with a few containers and Samba. I decided to try Proxmox following this guide: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm.

It all went fine, and I got to log into the web interface. That's where I got a little sidetracked, as I started to uninstall Docker, and decided to reboot before I got to the last step which is to create a Linux Bridge called vmbr0, and add my network interface to it. After that reboot, I'm no longer able to reach the web UI, the Samba share or SSH in using root (was not before either) or my user (which is what I used when I installed Proxmox in the first place). I can ping it, so I know it's running. I also tried to remove the relevant entries in known_hosts in case it had renewed the ssh key., but I still get Connection refused.

Is this because i forgot vmbr0, or is there something else I could try? As I mentioned, it's remote and I won't be able to physically access it for another 10 days. It's no big deal, but a bit unfortunate as I can't keep playing with it until then.

Bonus question: How can i create the vmbr0 from command line when I do get physical access?
 
No, not creating vmbr0 would not have caused you to lose network access to the host. In a standard installation, the IP simply moves from the physical interface to the virtual bridge interface, but the IP was already there.

It’s more likely that your Docker uninstallation did not go smoothly. Docker is quite intrusive when it comes to networking. When removing it, you should ensure that all virtual networks are properly removed and that the underlying physical interface is correctly configured before rebooting.

Bonus: You might find this resource helpful: Proxmox Network Configuration

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
baugen said:
So I have a remote test rig that i have been running Debian on, just testing some different setups. The only thing installed was Debian 12 with Docker with a few containers and Samba. I decided to try Proxmox following this guide: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm.

It all went fine, and I got to log into the web interface. That's where I got a little sidetracked, as I started to uninstall Docker, and decided to reboot before I got to the last step which is to create a Linux Bridge called vmbr0, and add my network interface to it. After that reboot, I'm no longer able to reach the web UI, the Samba share or SSH in using root (was not before either) or my user (which is what I used when I installed Proxmox in the first place). I can ping it, so I know it's running. I also tried to remove the relevant entries in known_hosts in case it had renewed the ssh key., but I still get Connection refused.

Is this because i forgot vmbr0, or is there something else I could try? As I mentioned, it's remote and I won't be able to physically access it for another 10 days. It's no big deal, but a bit unfortunate as I can't keep playing with it until then.

Bonus question: How can i create the vmbr0 from command line when I do get physical access?
Click to expand...
Did you enable Proxmox Virtual Environment firewall ?
 
You must log in or register to reply here.
Top Bottom