proxmox server no web access, gateway no ping

powerppc

New Member
Jun 11, 2023
1
0
1
Hi,

I was working normally with my promox server without any problem until today. When I started it, I couldn't access the web gui https://192.168.1.55:8006/
When I pinged from a pc on the same network I couldn't reach that ip so I connected to the promox server with the screen physically connected. after logging in, I checked the network configuration:

iface vmbr0 inet static​
address 192.168.1.55/24​
gateway 192.168.1.1​
bridge-ports enp4s0​
bridge-stp off​
bridge-fd 0​

I pinged the 192.168.1.1 gateway and it does not resolve.
Restart the network service with systemctl restart networking
and it is still the same. I have checked the services and they are up.
The computer is connected directly to the router by cable.


Could you help me?
 
Please provide the full output of: ip a in code-tags (or attach a good readable screenshot of it).
 
Hi,

I was working normally with my promox server without any problem until today. When I started it, I couldn't access the web gui https://192.168.1.55:8006/
When I pinged from a pc on the same network I couldn't reach that ip so I connected to the promox server with the screen physically connected. after logging in, I checked the network configuration:

iface vmbr0 inet static​
address 192.168.1.55/24​
gateway 192.168.1.1​
bridge-ports enp4s0​
bridge-stp off​
bridge-fd 0​

I pinged the 192.168.1.1 gateway and it does not resolve.
Restart the network service with systemctl restart networking
and it is still the same. I have checked the services and they are up.
The computer is connected directly to the router by cable.


Could you help me?

Very basic:
Check the utp cables visually (dog/cat can chew them..)
Also check all rj45 connectors if they are seated properly ("click" in switch port).

Ping does not "resolve" an address, it just sends an echo and receives a reply.
Did you mean : Reply from 192.168.1.1: Destination host unreachable.
Is 192.168.1.55 inside or outside your DHCP pool, maybe .55 is given to another device?

Have you tried rebooting your PVE host?