Search results

Thanks for the response. I'm in the process of restoring the system, and the issue just resurfaced. After a bit of digging, I realized what happened - I was passing through my GPU to one of my VMs. I removed the GPU, and on reboot apparently Proxmox decided that since it couldn't find the GPU it...

Alright, reinstall did the trick. `/etc/network/interfaces` is configured exactly as I had it, but `enp1s0` now shows up in `ip addr`. Here's what `dmesg | grep enp` looks like on a working system:

Alright, I'd love to work this out and post the solution here but I'm running out of time. Reinstalling Proxmox as soon as I finish pulling backups off.

Is it possibly an issue with the R8169 driver?

I cannot wrap my head around how it is possible that the ethernet link is down on Proxmox but one VM has network access. I am sure this is Linux networking 101 but it's beyond me. Anyone?

Had energy to do a bit more digging today. Running `ifreload -a` returns "Error: vmbr0: bridge port enp2s0 does not exist." So it seems like Proxmox is not seeing the physical ethernet port, though I'm not sure how a VM would have connectivity if this were the case. I read on another forum post...

I have had Proxmox up and running with no issues for over a year. Today I decided to move the Proxmox machine to a different ethernet port on my router (separate pfSense box) to put it in a DMZ. To make things easier, I configured the new interface in pfSense with all the same settings...

I figured it out - it had nothing to do with Proxmox. For some reason Ubuntu's firewall was blocking port 5000 but allowing 4000 through. I just added a rule to allow 5000 (sudo ufw allow 5000) and everything is working. Sorry for the trouble!

Here you are: qm config 100 agent: 1 balloon: 4096 boot: order=sata0;net0 cores: 4 ide2: local:iso/ubuntu-20.04.3-desktop-amd64.iso,media=cdrom,size=2999936K memory: 16384 name: Ubuntu net0: virtio=6A:41:B3:01:3D:61,bridge=vmbr0,firewall=1 numa: 0 onboot: 1 ostype: l26 sata0...

I've been running a service (OctoPrint) via Docker inside an Ubuntu VM. It has been working perfectly, with me able to access the service's web UI via port 4000 of the VM. I've had to switch this to a regular install (not inside Docker), and now it isn't working. While I can access the service...