[SOLVED] Can't Access Web Gui Only SSH

fvp1992

New Member
Jun 24, 2022
10
1
3
I was getting hostname error 5000 when attempting to access my proxmox VMs so I restarted the node and now I cannot access any of it through the Web UI. I can SSH to it but I am lost on what to do to resolve. I think I messed up changing hostnames as I recently got a new router.

Any help would be appreciated. I do not want to have to start over
 
If you manage to SSH in, then you know the IP_ADDRESS of your PVE.

What happens if you go to https://IP_ADDRESS:8006/
 
If you manage to SSH in, then you know the IP_ADDRESS of your PVE.

What happens if you go to https://IP_ADDRESS:8006/
Nothing happens, it times out.

I've been accessing it at this same IP address for years and used this IP to ssh to it.

Also when checking in my router leases it is not showing up as grabbing a new DHCP address.
 
I've been accessing it at this same IP address for years and used this IP to ssh to it.
I understand that presently you can SSH into it from a different machine. Is this the same machine that you're unable to connect to the Web UI?

Also show me the IP address (local) of the machine you're using to access PVE via SSH, and the command you're using to connect, which should include the IP address (local) of the PVE.

Also what is your router's Gateway.

Also what is the output of cat /etc/network/interfaces on the PVE. And the output of ip a and then also ip r please.

when checking in my router leases it is not showing up as grabbing a new DHCP address.

You should be using a Static address for your PVE. Preferably out of the DHCP range.
 
Last edited:
I understand that presently you can SSH into it. Show me the IP address (local) of the machine you're using to access PVE, and the command your using to connect, which should include the IP address (local) of the PVE. Also what is your router's Gateway.


Also what is the output of cat /etc/network/interfaces on the PVE.



You should be using a Static address for your PVE. Preferably out of the DHCP range.
  • IP address of PC I am accessing from: 192.168.100.32
    1710406616049.png
  • Trying to access PVE at: 192.168.100.15:8006
  • Newly setup OPNsense Gateway: 192.168.100.1
  • OPNsense uses 1.1.1.1 for DNS
  • Results of cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp6s0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.100.15/24
gateway 192.168.100.1
bridge-ports enp6s0
bridge-stp off
bridge-fd 0

iface wlp5s0 inet manual
 
Your reply is still incomplete (re-read my post for requested info).

However I notice that the machine you're using to try to connect from is on Wifi. Can you try and find a machine that is on the same wired Lan network as the PVE. (You may have a different network for Wifi in OPNsense).
 
Your reply is still incomplete (re-read my post for requested info).

However I notice that the machine you're using to try to connect from is on Wifi. Can you try and find a machine that is on the same wired Lan network as the PVE. (You may have a different network for Wifi in OPNsense).
Same results when attempting to access the Web UI from a wired LAN device.

root@ProxMox:~# ip a
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
valid_lft forever preferred_lft forever
2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 50:eb:f6:ce:32:2c brd ff:ff:ff:ff:ff:ff
3: wlp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether dc:21:5c:b3:a1:32 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 50:eb:f6:ce:32:2c brd ff:ff:ff:ff:ff:ff
inet 192.168.100.15/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::52eb:f6ff:fece:322c/64 scope link
valid_lft forever preferred_lft forever

root@ProxMox:~# ip r
default via 192.168.100.1 dev vmbr0 proto kernel onlink
192.168.100.0/24 dev vmbr0 proto kernel scope link src 192.168.100.15
 
All looks good
What is output of cat /etc/hosts
root@ProxMox:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.100.15 pve-cryo.home pve-cryo

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
root@ProxMox:~# cat /etc/hosts/
cat: /etc/hosts/: Not a directory
root@ProxMox:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.100.15 pve-cryo.home pve-cryo

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
 
This does not look good
Did you check if all services are running?
root@ProxMox:~# systemctl pveproxy.service
Unknown command verb pveproxy.service.
root@ProxMox:~# systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-03-13 20:06:42 EDT; 13h ago
Process: 1131 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=111)
Process: 1132 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Process: 10898 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS)
Main PID: 1135 (pveproxy)
Tasks: 4 (limit: 37592)
Memory: 135.0M
CPU: 10min 25.050s
CGroup: /system.slice/pveproxy.service
├─ 1135 pveproxy
├─34275 pveproxy worker
├─34276 pveproxy worker
└─34277 pveproxy worker

Mar 14 09:22:31 ProxMox pveproxy[34275]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1998.
Mar 14 09:22:34 ProxMox pveproxy[34273]: worker exit
Mar 14 09:22:34 ProxMox pveproxy[34274]: worker exit
Mar 14 09:22:34 ProxMox pveproxy[1135]: worker 34273 finished
Mar 14 09:22:34 ProxMox pveproxy[1135]: worker 34274 finished
Mar 14 09:22:34 ProxMox pveproxy[1135]: starting 2 worker(s)
Mar 14 09:22:34 ProxMox pveproxy[1135]: worker 34276 started
Mar 14 09:22:34 ProxMox pveproxy[1135]: worker 34277 started
Mar 14 09:22:34 ProxMox pveproxy[34276]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1998.
Mar 14 09:22:34 ProxMox pveproxy[34277]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1998.
Mar 14 09:22:36 ProxMox pveproxy[34275]: worker exit
Mar 14 09:22:36 ProxMox pveproxy[1135]: worker 34275 finished
Mar 14 09:22:36 ProxMox pveproxy[1135]: starting 1 worker(s)
Mar 14 09:22:36 ProxMox pveproxy[1135]: worker 34280 started
Mar 14 09:22:36 ProxMox pveproxy[34280]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1998.
 
It seems like you changed your hostname but perhaps not fully. Your shell shows that the host may be called "ProxMox", yet /etc/hosts contains "pve-cryo"
This can easily trip up multiple services, including PVE.

Go through the steps here https://pve.proxmox.com/wiki/Renaming_a_PVE_node and check all the relevant places.

Also, check available space on your root disk: df -h


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: fvp1992 and Dunuin
Ok this is the messed: As you see here your hostname is ProxMox (according to /etc/hostname)
BUT according to /etc/hosts its called "pve-cryo"
Thank you so much, saved me countless hours.

I updated /etc/hosts and am now able to see everything running. Time to do backups and more research before I resume any more tinkering.

root@ProxMox:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.100.15 ProxMox.home ProxMox

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
root@ProxMox:~#
 
  • Like
Reactions: showiproute

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!