I've been trying to find many fixed for not being able to access the web interface of Proxmox for about 2 weeks now. I have looked throughout the internet to try and find a fix for my issue but no posts have helped me. I have just finished getting the command line stuff done and have now moved onto trying to make VMs but can't access the web interface to make the VMs. I have put the correct web address in an I get a failed to connect error after about 1 minute. Any ideas for how this can be fixed?
Can't access the web interface of Proxmox
- Thread starter Arctic
- Start date
Hi @Arctic ,
What exact error are you getting in your browser?
Please answer these standard questions:
Can you ping the PVE server?
Can you ssh into PVE server?
What is the IP of the PVE server?
What is the IP of your workstation?
What is the IP of your gateway?
What is the output of "ip a" on PVE?
What is the corresponding output from your workstation? (ipconfig /all ; ip a)
What is the output of "curl -k https://127.0.0.1:8006" when run directly from PVE (over SSH or physical console?)
What is the output of "curl -k https://LAN_IP:8006" when run directly from PVE (over SSH or physical console?)
Good luck
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
What exact error are you getting in your browser?
Please answer these standard questions:
Can you ping the PVE server?
Can you ssh into PVE server?
What is the IP of the PVE server?
What is the IP of your workstation?
What is the IP of your gateway?
What is the output of "ip a" on PVE?
What is the corresponding output from your workstation? (ipconfig /all ; ip a)
What is the output of "curl -k https://127.0.0.1:8006" when run directly from PVE (over SSH or physical console?)
What is the output of "curl -k https://LAN_IP:8006" when run directly from PVE (over SSH or physical console?)
Good luck
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
The error I'm getting in my browser is that the ip address "took too long to respond".
Can you ping the PVE server: Yes.
Can you ssh into PVE server: Yes.
What is the IP of the PVE server: 192.168.175.138.
What is the IP of your workstation: 192.168.175.226.
What is the IP of your gateway: 192.168.175.254.
What is the output of "ip a" on PVE:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defult qluen 100
link/loopback 00:00:00:00:00:00 brb 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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qisc mq master vmbr0 state UP group default qlen 1000
link/ether a8:a1:59:f5:c6:09 brb ff:ff:ff:ff:ff:ff
altname enp66s0f0
3: eno2: <BROADCAST,MULTICAST> mtu 100 qdisc noop state DOWN group default qlen 1000
link/ether a8:a1:59:f5:c6:0a brb ff:ff:ff:ff:ff:ff
altname enp66s0f1
4: enx86b2d4a49462: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 86:b2:d4:a4:94:62 brb ff:ff:ff:ff:ff:ff:
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether a8:a1:59:f5:c6:09 brb ff:ff:ff:ff:ff:ff
inet 192.168.175.138/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::aaa1:59ff:fef5:c609/64 scope link
valid_lft forever preferred_lft forever
What is the corresponding output from your workstation:
Windows IP Configuration
Host Name . . . . . . . . . . . . : DESKTOP-2F2IS9V
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (4) I219-V
Physical Address. . . . . . . . . : 10-62-E5-F5-76-E7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 1:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 74-70-FD-DE-2C-CD
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 76-70-FD-DE-2C-CC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 8265
Physical Address. . . . . . . . . : 74-70-FD-DE-2C-CC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2855:120a:723b:a788%16(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.175.226(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, May 30, 2024 12:10:54 PM
Lease Expires . . . . . . . . . . : Saturday, June 1, 2024 11:55:42 AM
Default Gateway . . . . . . . . . : 192.168.175.254
DHCP Server . . . . . . . . . . . : 192.168.175.254
DHCPv6 IAID . . . . . . . . . . . : 259289341
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2D-54-55-1C-10-62-E5-F5-76-E7
DNS Servers . . . . . . . . . . . : 10.8.0.31
10.8.64.24
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 74-70-FD-DE-2C-D0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
What is the output of "curl -k https://127.0.0.1:8006" when run directly from PVE: It acts like it's trying to list something but doesn't list anything.
What is the output of "curl -k https://LAN_IP:8006" when run directly from PVE: It does the same thing as above^.
Can you ping the PVE server: Yes.
Can you ssh into PVE server: Yes.
What is the IP of the PVE server: 192.168.175.138.
What is the IP of your workstation: 192.168.175.226.
What is the IP of your gateway: 192.168.175.254.
What is the output of "ip a" on PVE:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defult qluen 100
link/loopback 00:00:00:00:00:00 brb 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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qisc mq master vmbr0 state UP group default qlen 1000
link/ether a8:a1:59:f5:c6:09 brb ff:ff:ff:ff:ff:ff
altname enp66s0f0
3: eno2: <BROADCAST,MULTICAST> mtu 100 qdisc noop state DOWN group default qlen 1000
link/ether a8:a1:59:f5:c6:0a brb ff:ff:ff:ff:ff:ff
altname enp66s0f1
4: enx86b2d4a49462: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 86:b2:d4:a4:94:62 brb ff:ff:ff:ff:ff:ff:
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether a8:a1:59:f5:c6:09 brb ff:ff:ff:ff:ff:ff
inet 192.168.175.138/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::aaa1:59ff:fef5:c609/64 scope link
valid_lft forever preferred_lft forever
What is the corresponding output from your workstation:
Windows IP Configuration
Host Name . . . . . . . . . . . . : DESKTOP-2F2IS9V
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (4) I219-V
Physical Address. . . . . . . . . : 10-62-E5-F5-76-E7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 1:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 74-70-FD-DE-2C-CD
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 76-70-FD-DE-2C-CC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 8265
Physical Address. . . . . . . . . : 74-70-FD-DE-2C-CC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2855:120a:723b:a788%16(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.175.226(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, May 30, 2024 12:10:54 PM
Lease Expires . . . . . . . . . . : Saturday, June 1, 2024 11:55:42 AM
Default Gateway . . . . . . . . . : 192.168.175.254
DHCP Server . . . . . . . . . . . : 192.168.175.254
DHCPv6 IAID . . . . . . . . . . . : 259289341
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2D-54-55-1C-10-62-E5-F5-76-E7
DNS Servers . . . . . . . . . . . : 10.8.0.31
10.8.64.24
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 74-70-FD-DE-2C-D0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
What is the output of "curl -k https://127.0.0.1:8006" when run directly from PVE: It acts like it's trying to list something but doesn't list anything.
What is the output of "curl -k https://LAN_IP:8006" when run directly from PVE: It does the same thing as above^.
Please use CODE tags for copy/paste output.
What is the output of : pveversion -v
What is the output of : systemctl |grep pve
How did you install the PVE? (PVE ISO, PVE over Debian)
What is the output of: dpkg --verify
Did you modify PVE by applying 3rd party patches?
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
What is the output of : pveversion -v
What is the output of : systemctl |grep pve
How did you install the PVE? (PVE ISO, PVE over Debian)
What is the output of: dpkg --verify
Did you modify PVE by applying 3rd party patches?
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
What is the output of : pveversion -v:
What is the output of : systemctl |grep pve:
How did you install the PVE? (PVE ISO, PVE over Debian): PVE ISO.
What is the output of: dpkg --verify:
Did you modify PVE by applying 3rd party patches: I believe so, I'm not sure because I was following a tutorial and just entered in the commands it told me to enter. But I think I remember needing to download something from a specific IP address.
Code:
proxmox-ve 7.4-1 (running kernel: 5.15.102-1-pve)
pve-manager: 7.4-3 (running version 7.4-3/9002ab8a)
pve-kernel-5.15: 7.3-3
pve-kernel-5.25.102-pve: 5.15.102-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-1
libpve-apiclient-perl:3.2-1
libpve-common-perl: 7.3-3
libpve-guest-common-perl:4.2-4
libpve-http-server-perl: 4.2-1
libpve-rs-perl: 0.7.5
lipve-storage-perl: 7.4-2
libqb0: no correctly installed
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.3.3-1
proxmox-bacup-file-restore: 2.3.3-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.6.3
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs:7.4-2
pve-edk2-firmware: 3.20221111-1
pve-firewall: 4.3-1
pve-firmware- 3.6-4
pve-ha-manager: 3.6.0
pve-il8n: 2.11-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0`bpoll+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1
Code:
pve-cluster.service loaded failed failed The Proxmox VE cluster filesystem
pve-daily-update.service loaded failed failed Daily PVE downlaod activities
pve-fiewall.service loaded failed failed Proxmox VE firewall
pve-guests.service loaded failed failed PVE guests
pve-ha-crm.service loaded failed failed PVE Cluster HA Resource Manager Daemon
pve-ha-lrm.service loaded failed failed PVE Loacl HA Resource Manager Daemon
pve-lxc-syscalid.service loaded active running Proxmox VE LXC Syscall Daemon
pvebanner.service loaded active exited Proxmox VE Login Banner
pvedaemon.service loaded active running PVE API Daemon
pvefw-logger.service loaded active running Proxmox VE firewall logger
pvenetcommit.service loaded active exited Commit Proxmox VE network changes
pveproxy.service loaded active running PVE API Proxy Server
pvescheduler.service loaded failed failed Proxmox VE scheduler
pvestatd.service loaded failed failed PVE Status Daemon
dev-pve-swap.swap loaded active active /dev/pve/swap
pve-storage.target loaded active active PVE Storage Target
pve-daily-update.timer loaded active waiting Daily PVE download activitiesWhat is the output of: dpkg --verify:
Code:
??5?????? c /et/apt/sources.list.d/pve-enterprise.list
??5?????? c /etc/lm/lvm.confg
??5?????? c /etc/issue
It acted like it was looking to write more but wouldn't.Do you have any free space left?
"df -h"
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
"df -h"
I would find the tutorial and review the steps. It is dangerous to blindly follow random "tutorials" on the net.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Do you have any free space left: Yes. 9.8GB/84GB on /, 126GB on /dev, 23MB/2GB on /run, 126GB on /dev/shm, 5MB on /run/lock, and 26GB on /run/user/0.
I would find the tutorial and review the steps. It is dangerous to blindly follow random "tutorials" on the net: it was a tutorial made by my friend, not from the net.
I would find the tutorial and review the steps. It is dangerous to blindly follow random "tutorials" on the net: it was a tutorial made by my friend, not from the net.
Based on the status of the services in the provided output, it seems like continuing to troubleshoot and recover your current system might not be the best use of your time.
I recommend reinstalling the system following the official installation procedure. Once you've got everything up and running smoothly, you can then customize it to suit your needs.
Best of luck!
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
I recommend reinstalling the system following the official installation procedure. Once you've got everything up and running smoothly, you can then customize it to suit your needs.
Best of luck!
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox