Proxmox VE no connection

TKL

New Member
Apr 22, 2025
19
0
1
Hey everyone, i am pretty new to the hole proxmox thing. i have read threw a few post that describe a similar problem as i have but havent found my issue exactly.
my Server doesn't show up in the connected devices of my router. but my switch seems to work fine (other devices plugged into it are working fine and connection lights are also lit. i can also not ping the server or open the webinterface.
i saw in some of the other posts, that people should check "systemctl status networking" and then "systemctl restart networking" i have attached the output (already looks like there is stuff broken.
i also attached my ip addr show (i think the bridge is missing for some reason but not sure)

Thanks for any help!
Kind regards
Timmy
 

Attachments

  • IMG_0204_2025-04-22_08_23_58.jpg
    IMG_0204_2025-04-22_08_23_58.jpg
    666.3 KB · Views: 9
  • IMG_0205_2025-04-22_08_23_10.jpg
    IMG_0205_2025-04-22_08_23_10.jpg
    423.3 KB · Views: 9
Hi,

i also attached my ip addr show (i think the bridge is missing for some reason but not sure)
yeah, looks like it.
How did you install Proxmox VE? Did you use the latest ISO?

What hardware are you running it on?
What is the content of /etc/network/interfaces?
 
hey thanks for the quick reply,
i downloaded the iso yesterday so yea it should be the newest (proxmox-ve_8.4-1.iso). i then created a bootdrive with rufus and installed it.
i am running it on my old pc (i7 6700k, 32gb ram, some random 500G m.2 ssd and a gtx 1070)
i attached the content of interfaces
 

Attachments

  • IMG_0206_2025-04-22_09_27_27(2).jpg
    IMG_0206_2025-04-22_09_27_27(2).jpg
    815.3 KB · Views: 8
Last edited:
Code:
iface enp6s0 inet dhcp

Did you modify /etc/network/interfaces by yourself? Proxmox VE never sets the dhcp option on the interface.

Instead try setting this line to
Code:
iface enp6s0 inet manual
which would be correct.
 
ah yes i forgot to mention that. i also saw that in another post. but i also had the problem, when it was still on manual. i have switched it back and rebooted and it hasnt changed anything
 
Seems some other service is failing and/or ifupdown2 hangs ..

What does systemctl status --failed report?
Did you fully reboot the system after performing above change?

You might also want to look at the full system log journalctl -b and see if there are any other warnings/errors/etc.
 
not sure what counts as warnings errors but i just photographed everything that was coloured orange.
 

Attachments

  • 20250422_112919559_iOS (Large).jpg
    20250422_112919559_iOS (Large).jpg
    560 KB · Views: 7
  • 20250422_112939030_iOS (Large).jpg
    20250422_112939030_iOS (Large).jpg
    426.6 KB · Views: 6
  • 20250422_112957454_iOS (Large).jpg
    20250422_112957454_iOS (Large).jpg
    504.6 KB · Views: 6
  • 20250422_113035563_iOS.jpg
    20250422_113035563_iOS.jpg
    861.1 KB · Views: 7
  • 20250422_112906051_iOS (Large).jpg
    20250422_112906051_iOS (Large).jpg
    471.7 KB · Views: 6
  • 20250422_112847704_iOS (Large).jpg
    20250422_112847704_iOS (Large).jpg
    458.4 KB · Views: 5
  • 20250422_112829563_iOS.jpg
    20250422_112829563_iOS.jpg
    930.3 KB · Views: 5
  • 20250422_112810602_iOS (Large).jpg
    20250422_112810602_iOS (Large).jpg
    508.7 KB · Views: 6
  • 20250422_112742353_iOS.jpg
    20250422_112742353_iOS.jpg
    916.6 KB · Views: 7
  • 20250422_112630364_iOS.jpg
    20250422_112630364_iOS.jpg
    749.2 KB · Views: 7
I would recommend confirming that the interface is set to manual, reboot, check the state of the network "ip a". If it still is not working - try to restart the service: systemctl restart networking. Provide updated screenshots of : ip a, /etc/networking/interfaces, journalctl -n 100

Another option - set the IP manually after boot. If that works, you will have better access to the system and troubleshooting:
https://access.redhat.com/sites/def...s/rh_ip_command_cheatsheet_1214_jcs_print.pdf


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
i'll try the manual ip later
 

Attachments

  • 20250422_132823931_iOS (Large).jpg
    20250422_132823931_iOS (Large).jpg
    487.4 KB · Views: 4
  • 20250422_132812001_iOS (Large).jpg
    20250422_132812001_iOS (Large).jpg
    412.1 KB · Views: 5
  • 20250422_132743339_iOS (Large).jpg
    20250422_132743339_iOS (Large).jpg
    183.5 KB · Views: 5
  • 20250422_132715550_iOS (Large).jpg
    20250422_132715550_iOS (Large).jpg
    281.2 KB · Views: 6
when i look at ip a, these ip adresses look very much like ipv6 adresses. my network only has ipv4 does this have anything to do with my issue?
edit: i am dumb and got mixed up. that obv is a mac address
 
Last edited:
ok update: i did the following:
Assign IP: ip addr add 192.168.178.32/24 dev enp6s0
set default gateway: ip route add default via 192.168.178.1
ip link set dev enp6s0 up


now i can ping my router and can also bring up the Dashboard.
my question now is: are these changes permanent, or do i have to do this everytime i restart the server?
 
it seems like the server now can connect to the local network but i still cant ping google etc.
 

Attachments

  • 1745341880044.png
    1745341880044.png
    31.9 KB · Views: 3
Code:
root@pve:~# ip route show
default via 192.168.178.1 dev enp6s0
192.168.178.0/24 dev enp6s0 proto kernel scope link src 192.168.178.32
yes
 
Code:
root@pve:~# ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.178.32 icmp_seq=1 Destination Host Unreachable
From 192.168.178.32 icmp_seq=2 Destination Host Unreachable
From 192.168.178.32 icmp_seq=3 Destination Host Unreachable
From 192.168.178.32 icmp_seq=4 Destination Host Unreachable

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3053ms
pipe 4
root@pve:~# ip route show
default via 192.168.178.1 dev enp6s0
192.168.178.0/24 dev vmbr0 proto kernel scope link src 192.168.178.32
root@pve:~# ping -c 4 192.168.178.1
PING 192.168.178.1 (192.168.178.1) 56(84) bytes of data.
64 bytes from 192.168.178.1: icmp_seq=1 ttl=64 time=3.82 ms
64 bytes from 192.168.178.1: icmp_seq=2 ttl=64 time=1.69 ms
64 bytes from 192.168.178.1: icmp_seq=3 ttl=64 time=3.52 ms
64 bytes from 192.168.178.1: icmp_seq=4 ttl=64 time=2.68 ms

--- 192.168.178.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 1.685/2.927/3.824/0.831 ms
root@pve:~# traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  pve.fritz.box (192.168.178.32)  3102.235 ms !H  3102.218 ms !H  3102.210 ms !H
in short: i can ping my router, it works, i can't ping 8.8.8.8
 
This is not a PVE issue. It is a basic Linux networking misconfiguration problem.

As you are running inside a hosting provider, you should reach out to them to confirm that you programmed your Debian Linux (which PVE is under the covers) with proper networking configuration.
Check that you are using the correct IP for GW, confirm the subnet mask, etc. Your service provider should be able to assist as they have the best knowledge about the proper settings for your particular instance.

Cheers


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox