Can't connect to Proxmox GUI

A

Arity

New Member
Dec 5, 2025
9
0
1
I am new to homelabbing and was able to set Proxmox up with a couple of containers and VMs. Suddenly everything disconnected so I tried rebooting the server and now I can't access the server remotely through Web GUI nor SSH. On the server itself, I can't ping 1.1.1.1 nor google either. I've tried everything I could following google but nothing seems to be helping. I'm at a loss as to what to do.
 
Have you checked that all cables are plugged in correctly at the server and the switch/router?
Run the command ip a on the server and post the output here.
 
All the cables should be plugged in fine as it used to work fine.

ip a returns:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: nic0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether d4:5d:64:54:3e:be brd ff:ff:ff:ff:ff:ff
altname enxd45d64543ebe
3: wlp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether d8:3b:bf:d9:a65:fc brd ff:ff:ff:ff:ff:ff
altname wlxd83bbfd9a6fc
 
Arity said:
All the cables should be plugged in fine as it used to work fine.
Click to expand...
If you say so...
The server has two network interfaces, a cable based one and a wireless adapter. Both report state DOWN. Which one were you using to connect the server to the network?
And would you like to post the content of file /etc/network/interfaces, too?
 
I was using nic0.

/etc/network/interfaces returns:

auto lo
iface lo inet loopback

iface nic0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.18/24
gateway 192.168.1.1
bridge_ports nic0
bridge_stp off
bridge_fd 0


source /etc/network/interfaces.d/*
 
Edit the file and put auto nic0 right above the line with iface nic0 inet manual
Save the change and afterwards run ifreload -a
 
ifreload -areturns:


File "/usr/share/ifupdoun2/ifupdown/scheduler.py", line 325, in run_iface_list
cls.run_iface_graph(ifupdanobifacenane, ps, parent,order, folloudependents)

File "usr/share/ifupdown?/ifupdown/scheduler.py", line 315, in run_iface_graph
cls.run_iface_list_ops(ifupdownobj, ifaceobjs, ops)

File "/usr/share/ifupdoun2/ifupdown/scheduler.py", line 188, in run_iface_list_ops
cls.run_iface_op(ifupdownobj, ifaceobj,op,
cenv+ifupdownobj.generate_running_env(ifaceobj, op)
if ifupdownobj.config.get('addon_scripts_support',
'0')== '1' else None)

File "/usr/share/ifupdoun2/ifupdown/scheduler.py", line 150, in run_iface_op
ifupdownobj.log_error('%s: %s %s' % (ifacename, op, str(e)))

File "usr/share/ifupdoun?/ifupdown/ifupdownmain.py", line 226, in log_error
raise Exception(str)
error: lo: lo; up cmd '/etc/network/if-up.d/chrony' failed: returned 1
File "usr/share/ifupdown2/ifupdoun/scheduler-py", line 325, in run_iface_list
cls.run_iface_graph(ifupdownobj, ifacename, ops, partent,
order, followdependents)

File "usr/share/ifupdoun?/ifupdown/scheduler.py", line 302, in run_iface_graph
cls.run_iface_list(ifupdownobj, dlist, ops,
ifacename, ordser,
followdependents,
continueonfailure=False)

File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 337, in run_iface_list
raise Exception('% s : (%s)' %(ifacename, str(e)))

error: vmbr0: nic0: (nic0: up cmd '/etc/network/if-up.d/chrony' failed: returned 1)
warning: vmbr0: interface not recognized - please check interface configuration
 
returned:

warning: lo: up cmd '/etc/network/if-up.d/chrony' failed ([Errno 13] Permission denied: ' /etc/network/if-up.d/chrony' )
warning: nic0: up cmd '/etc/network/if-up.d/chrony' failed ([Errno 13] Permission denied: '/etc/network/if-up.d/chrony' )
warning: vmbr0: up cmd '/etc/network/if-up.d/chrony' failed ([Errno 13] Permission denied: '/etc/network/if-up.d/chrony' )
 
ip a returns:

1: lo: <LOOPBACK,UP, LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_Ift forever preferred_Ift forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_Ift forever
2: nic0: <BROADCAST, MULTICAST, UP ,LOWER UP> mtu 1500 qdisc fq_codel master vmbr0 state UP group default qlen 1000
link/ether d4:5d:64:54:3e:be brd ff:ff:ff:ff:ff:ff
altname enxd45d64543ebe
3: wlp4s0: <BROADCAST, MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether d8:3b:bf:d9:a6:fc brd ff:ff:ff:ff:ff:ff
altname wlxd83bbfd9a6fc
4: vmbr0: <BROADCAST, MULTICAST,UP, LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether d4:5d:64:54:3e:be brd ff:ff:ff:ff:ff:ff
inet 192.168.1.18/24 scope global vmbr0
valid_lft forever preferred_Ift forever
inet6 fe80::d65d:64ff:fe51:3ebe/64 scope link proto kernel_ll
valid_lft forever preferred_Ift forever
 
That's looking good. Assuming the ip address configuration is correct, the server should be available again at 192.168.1.18/24
 
can you ping the server from your desktop ping 192.168.1.18?
What is the output of systemctl status pveproxy on the server? Post the output in as code, this makes it easier to read. Use this icon in the post for that 1765186581162.png
 
Last edited:
Ping 192.168.1.18 works on deskstop. I feel hopeful!

Code: 
systemctl status pveproxy
returns:

Code: 
*pveproxy service - PVE API Proxy Server
Loaded: loaded (/usr/lib/systend/system/pveproxy.service; enabled: preset: enabled)
Active: active (running) since Sun 2025-12-07 11:47:30 CST: 21h ago
Invocation: 593cc0f2d5e94c5384366cfccdf069ef
Process: 1224 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 1228 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Process: 1238 ExecStartPost=sh -c [ ! -e /var/log/pveam.log ] && /usr/bin/pveupdate (code=exited, status=1/FAILURE)
Main PID: 1233 (pveproxy)
Tasks: 4 (limit: 96172)
Menory: 163.5M (peak: 222.2M)
CPU: 19min 34.646s
CGroup:/system.slice/pveproxy.service
-1233 pueproxy
-269976 "pvepraxy worker"
-269977 "pveproxy worker"
-269978 "pveproxy worker"

Dec 08 09:46:28 pveproxy [1233]: starting 2 worker (s)
Dec 08 09:46:28 pveproxy [1233]: worker 269976 started
Dec 08 09:46:28 pveproxy [1233]: worker 269977 started
Dec 08 09:46:28 pveproxy [269968]: worker exit
Dec 08 09:46:28 pveproxy [269976]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Dec 08 09:46:28 pveproxy [269977]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Dec 08 09:46:28 pveproxy [1233]: worker 269968 finished
Dec 08 09:46:28 pveproxy [1233]: starting 1 worker(s)
Dec 08 09:46:28 pveproxy [1233]: worker 269978 started
Dec 08 09:46:28 pveproxy [269978]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
 
You must log in or register to reply here.
Top Bottom