Trouble connecting to the Proxmox Server after the initial start-up.

Mario021

New Member
May 31, 2023
3
0
1
Hi there, I am new to Proxmox and networking, and currently using a Dell Poweredge R720xd system with Proxmox 7.3. I have set up Proxmox on a static port with 192.168.42.196, and it was working perfectly fine until I started using IDRAC on a separate static port with 192.168.42.200. The IDRAC is on a dedicated network card, while Proxmox is connected to a separate one.

Initially, after a reboot, I could access the UI and ping the server on the static port. However, after a few minutes, the web UI stopped working, and I received an error message stating that the site can't be reached. When I tried pinging Proxmox, I got a "Destination host unreachable" message, just like when I used Proxmox to ping out.

I have searched for similar issues, but so far, I haven't found any solution.
 

Attachments

  • Screenshot 2023-05-31 102546.png
    Screenshot 2023-05-31 102546.png
    15.5 KB · Views: 5
  • Screenshot 2023-05-31 102713.png
    Screenshot 2023-05-31 102713.png
    3.6 KB · Views: 6
  • Screenshot 2023-05-31 102812.png
    Screenshot 2023-05-31 102812.png
    16.4 KB · Views: 7
  • Screenshot 2023-05-31 103339.png
    Screenshot 2023-05-31 103339.png
    123.1 KB · Views: 6
  • Screenshot 2023-05-31 103924.png
    Screenshot 2023-05-31 103924.png
    51.1 KB · Views: 5
Last edited:
Hi, vmbr0 is down, hence no network connectivity. Please check the status of systemctl status networking.service and try to bring the bridge up by running ip link set vmbr0 up.

Edit: Also, NO-CARRIER might indicate that the NIC is not connected correctly. Did you install the second network interface afterwards? Maybe the interface names changed? Check via ip link show.
 
Last edited:
Hello Chris,

I believe that NO-CARRIER is the issue. It has a different Mac Address.
 

Attachments

  • Screenshot 2023-05-31 110532.png
    Screenshot 2023-05-31 110532.png
    46.9 KB · Views: 7
  • Screenshot 2023-05-31 110636.png
    Screenshot 2023-05-31 110636.png
    95.7 KB · Views: 7
  • Screenshot 2023-05-31 111555.png
    Screenshot 2023-05-31 111555.png
    20.3 KB · Views: 7
Hello Chris,

I believe that NO-CARRIER is the issue. It has a different Mac Address.
No, your issue here is that eno1 is not present anymore as you can see from the error in the systemctl status networking.service. As a matter of fact, non of the enoX links is listed in the output.
 
I have identified my mistake in setting up a PCI passthrough for a VM. I inadvertently passed my main NIC, which was being used by Proxmox. Upon investigation, I realized that the VM was set to delay auto-starting. This resulted in losing connection a few minutes after rebooting. To resolve the issue, I removed the PCI passthrough for that VM and created a vmbr1 with the correct NIC, which resolved the problem. Thank you!
 

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!