The web interface does not open after installation

S

soblod

New Member
Mar 4, 2024
5
0
1
Hello everyone, I downloaded the latest image of proxmox-ve_8.1-2 from the site, installed it, set all the parameters, specified the IP address, the server rebooted, the IP address is available using the PING command, but the web interface does not work, my address is 172.18.200.9:8006 I reinstalled it several times, the problem persisted, it’s also not available in other browsers, it’s not available on another computer or phone
 
soblod said:
Mr.Doubt said:
Did you try https.//172.18.200.9:8006
Click to expand...
yes of course it doesn't work either
Click to expand...
That won't work because there is a . after the https instead of a :.

Can you SSH into the Proxmox host? Otherwise, log into the Proxmox host console using a physical keyboard and display. Are there any relevant error messages in journalctl -b 0 -e (you will have to scroll with the arrow keys to look for them)?

What is the output of curl -k https://172.18.200.9:8006 (when run from the Proxmox host itself)? What is the output of ip a? What is the output of cat /etc/network/interfaces? What is the output of systemctl status pve-*?
 
That won't work because there is a . after the https instead of a :.
Click to expand...
yes, I noticed it :), I entered it correctly with:

Can you SSH into the Proxmox host? Otherwise, log into the Proxmox host console using a physical keyboard and display. Are there any relevant error messages in journalctl -b 0 -e (you will have to scroll with the arrow keys to look for them)?
Click to expand...
I can log in via ssh and log in

journalctl -b 0 -e
Click to expand...
вот последние строчки

Mar 04 11:10:11 PM-00vallexm pveproxy[3003]: worker exit
Mar 04 11:10:11 PM-00vallexm pveproxy[3004]: worker exit
Mar 04 11:10:11 PM-00vallexm pveproxy[1199]: worker 3003 finished
Mar 04 11:10:11 PM-00vallexm pveproxy[1199]: starting 1 worker(s)
Mar 04 11:10:11 PM-00vallexm pveproxy[1199]: worker 3006 started
Mar 04 11:10:11 PM-00vallexm pveproxy[1199]: worker 3004 finished
Mar 04 11:10:11 PM-00vallexm pveproxy[1199]: starting 1 worker(s)
Mar 04 11:10:11 PM-00vallexm pveproxy[1199]: worker 3007 started
Mar 04 11:10:11 PM-00vallexm pveproxy[3006]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServe>
Mar 04 11:10:11 PM-00vallexm pveproxy[3007]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServe>
Mar 04 11:10:16 PM-00vallexm pveproxy[3005]: worker exit
Mar 04 11:10:16 PM-00vallexm pveproxy[1199]: worker 3005 finished
Mar 04 11:10:16 PM-00vallexm pveproxy[1199]: starting 1 worker(s)
Mar 04 11:10:16 PM-00vallexm pveproxy[1199]: worker 3008 started
Mar 04 11:10:16 PM-00vallexm pveproxy[3008]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServe>
Mar 04 11:10:16 PM-00vallexm pveproxy[3006]: worker exit
Mar 04 11:10:16 PM-00vallexm pveproxy[3007]: worker exit
Mar 04 11:10:16 PM-00vallexm pveproxy[1199]: worker 3006 finished
Mar 04 11:10:16 PM-00vallexm pveproxy[1199]: starting 1 worker(s)
Mar 04 11:10:16 PM-00vallexm pveproxy[1199]: worker 3009 started
Mar 04 11:10:16 PM-00vallexm pveproxy[1199]: worker 3007 finished
Mar 04 11:10:16 PM-00vallexm pveproxy[1199]: starting 1 worker(s)
Mar 04 11:10:16 PM-00vallexm pveproxy[1199]: worker 3010 started
Mar 04 11:10:16 PM-00vallexm pveproxy[3009]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServe>
Mar 04 11:10:16 PM-00vallexm pveproxy[3010]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServe>


curl -k https://172.18.200.9:8006
Click to expand...
no result

ip a
Click to expand...
result

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: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether f0:79:59:90:6e:51 brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether f0:79:59:90:6e:51 brd ff:ff:ff:ff:ff:ff
inet 172.18.200.9/16 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::f279:59ff:fe90:6e51/64 scope link
valid_lft forever preferred_lft forever


cat /etc/network/interfaces
Click to expand...

result

auto lo
iface lo inet loopback

iface enp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
address 172.18.200.9/16
gateway 172.18.0.1
bridge-ports enp3s0
bridge-stp off
bridge-fd 0

systemctl status pve-*
Click to expand...

result

● pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon
Loaded: loaded (/lib/systemd/system/pve-lxc-syscalld.service; enabled; preset: enabled)
Active: active (running) since Mon 2024-03-04 10:16:16 MSK; 1h 1min ago
Main PID: 683 (pve-lxc-syscall)
Tasks: 5 (limit: 4456)
Memory: 1.3M
CPU: 3ms
CGroup: /system.slice/pve-lxc-syscalld.service
└─683 /usr/lib/x86_64-linux-gnu/pve-lxc-syscalld/pve-lxc-syscalld --system /run/pve/lxc-syscalld.sock

Mar 04 10:16:16 PM-00vallexm systemd[1]: Starting pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon...
Mar 04 10:16:16 PM-00vallexm systemd[1]: Started pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon.

× pve-guests.service - PVE guests
Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2024-03-04 10:16:27 MSK; 1h 1min ago
Process: 896 ExecStartPre=/usr/share/pve-manager/helpers/pve-startall-delay (code=exited, status=0/SUCCESS)
Process: 897 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=111)
Main PID: 897 (code=exited, status=111)
CPU: 957ms

Mar 04 10:16:26 PM-00vallexm systemd[1]: Starting pve-guests.service - PVE guests...
Mar 04 10:16:27 PM-00vallexm pvesh[897]: ipcc_send_rec[1] failed: Connection refused
Mar 04 10:16:27 PM-00vallexm pvesh[897]: ipcc_send_rec[2] failed: Connection refused
Mar 04 10:16:27 PM-00vallexm pvesh[897]: ipcc_send_rec[3] failed: Connection refused
Mar 04 10:16:27 PM-00vallexm pvesh[897]: Unable to load access control list: Connection refused
Mar 04 10:16:27 PM-00vallexm systemd[1]: pve-guests.service: Main process exited, code=exited, status=111/n/a
Mar 04 10:16:27 PM-00vallexm systemd[1]: pve-guests.service: Failed with result 'exit-code'.
Mar 04 10:16:27 PM-00vallexm systemd[1]: Failed to start pve-guests.service - PVE guests.

× pve-ha-lrm.service - PVE Local HA Resource Manager Daemon
Loaded: loaded (/lib/systemd/system/pve-ha-lrm.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2024-03-04 10:16:26 MSK; 1h 1min ago
Process: 892 ExecStart=/usr/sbin/pve-ha-lrm start (code=exited, status=111)
CPU: 651ms

Mar 04 10:16:26 PM-00vallexm pve-ha-lrm[892]: ipcc_send_rec[1] failed: Connection refused
Mar 04 10:16:26 PM-00vallexm pve-ha-lrm[892]: ipcc_send_rec[2] failed: Connection refused
Mar 04 10:16:26 PM-00vallexm pve-ha-lrm[892]: ipcc_send_rec[3] failed: Connection refused
Mar 04 10:16:26 PM-00vallexm pve-ha-lrm[892]: ipcc_send_rec[1] failed: Connection refused
Mar 04 10:16:26 PM-00vallexm pve-ha-lrm[892]: ipcc_send_rec[2] failed: Connection refused
Mar 04 10:16:26 PM-00vallexm pve-ha-lrm[892]: Unable to load access control list: Connection refused
Mar 04 10:16:26 PM-00vallexm pve-ha-lrm[892]: ipcc_send_rec[3] failed: Connection refused
Mar 04 10:16:26 PM-00vallexm systemd[1]: pve-ha-lrm.service: Control process exited, code=exited, status=111/n/a
Mar 04 10:16:26 PM-00vallexm systemd[1]: pve-ha-lrm.service: Failed with result 'exit-code'.
Mar 04 10:16:26 PM-00vallexm systemd[1]: Failed to start pve-ha-lrm.service - PVE Local HA Resource Manager Daemon.

× pve-firewall.service - Proxmox VE firewall
Loaded: loaded (/lib/systemd/system/pve-firewall.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2024-03-04 10:16:23 MSK; 1h 1min ago
Process: 871 ExecStartPre=/usr/bin/update-alternatives --set ebtables /usr/sbin/ebtables-legacy (code=exited, status=0/SUCCESS)
Process: 874 ExecStartPre=/usr/bin/update-alternatives --set iptables /usr/sbin/iptables-legacy (code=exited, status=0/SUCCESS)
Process: 875 ExecStartPre=/usr/bin/update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy (code=exited, status=0/SUCCESS)
Process: 876 ExecStart=/usr/sbin/pve-firewall start (code=exited, status=111)
CPU: 841ms

Mar 04 10:16:23 PM-00vallexm pve-firewall[876]: ipcc_send_rec[1] failed: Connection refused
Mar 04 10:16:23 PM-00vallexm pve-firewall[876]: ipcc_send_rec[2] failed: Connection refused
Mar 04 10:16:23 PM-00vallexm pve-firewall[876]: ipcc_send_rec[1] failed: Connection refused
Mar 04 10:16:23 PM-00vallexm pve-firewall[876]: ipcc_send_rec[2] failed: Connection refused
Mar 04 10:16:23 PM-00vallexm pve-firewall[876]: ipcc_send_rec[3] failed: Connection refused
Mar 04 10:16:23 PM-00vallexm pve-firewall[876]: ipcc_send_rec[3] failed: Connection refused
Mar 04 10:16:23 PM-00vallexm pve-firewall[876]: Unable to load access control list: Connection refused
Mar 04 10:16:23 PM-00vallexm systemd[1]: pve-firewall.service: Control process exited, code=exited, status=111/n/a
Mar 04 10:16:23 PM-00vallexm systemd[1]: pve-firewall.service: Failed with result 'exit-code'.
Mar 04 10:16:23 PM-00vallexm systemd[1]: Failed to start pve-firewall.service - Proxmox VE firewall.

● pve-storage.target - PVE Storage Target
Loaded: loaded (/lib/systemd/system/pve-storage.target; static)
Active: active since Mon 2024-03-04 10:16:17 MSK; 1h 1min ago

Mar 04 10:16:17 PM-00vallexm systemd[1]: Reached target pve-storage.target - PVE Storage Target.

● pve-daily-update.timer - Daily PVE download activities
Loaded: loaded (/lib/systemd/system/pve-daily-update.timer; enabled; preset: enabled)
Active: active (waiting) since Mon 2024-03-04 10:16:17 MSK; 1h 1min ago
Trigger: Tue 2024-03-05 03:33:22 MSK; 16h left
Triggers: ● pve-daily-update.service

Mar 04 10:16:17 PM-00vallexm systemd[1]: Started pve-daily-update.timer - Daily PVE download activities.

× pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon
Loaded: loaded (/lib/systemd/system/pve-ha-crm.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2024-03-04 10:16:24 MSK; 1h 1min ago
Process: 885 ExecStart=/usr/sbin/pve-ha-crm start (code=exited, status=111)
CPU: 641ms

Mar 04 10:16:24 PM-00vallexm pve-ha-crm[885]: ipcc_send_rec[1] failed: Connection refused
Mar 04 10:16:24 PM-00vallexm pve-ha-crm[885]: ipcc_send_rec[2] failed: Connection refused
Mar 04 10:16:24 PM-00vallexm pve-ha-crm[885]: ipcc_send_rec[3] failed: Connection refused
Mar 04 10:16:24 PM-00vallexm pve-ha-crm[885]: ipcc_send_rec[1] failed: Connection refused
Mar 04 10:16:24 PM-00vallexm pve-ha-crm[885]: ipcc_send_rec[2] failed: Connection refused
Mar 04 10:16:24 PM-00vallexm pve-ha-crm[885]: Unable to load access control list: Connection refused
Mar 04 10:16:24 PM-00vallexm pve-ha-crm[885]: ipcc_send_rec[3] failed: Connection refused
Mar 04 10:16:24 PM-00vallexm systemd[1]: pve-ha-crm.service: Control process exited, code=exited, status=111/n/a
Mar 04 10:16:24 PM-00vallexm systemd[1]: pve-ha-crm.service: Failed with result 'exit-code'.
Mar 04 10:16:24 PM-00vallexm systemd[1]: Failed to start pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon.

× pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2024-03-04 10:23:07 MSK; 54min ago
Process: 1198 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
CPU: 9ms

Mar 04 10:23:07 PM-00vallexm systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Mar 04 10:23:07 PM-00vallexm systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
Mar 04 10:23:07 PM-00vallexm systemd[1]: pve-cluster.service: Start request repeated too quickly.
Mar 04 10:23:07 PM-00vallexm systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Mar 04 10:23:07 PM-00vallexm systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
lines 51-109/109 (END)
 
soblod said:
Mar 04 11:10:11 PM-00vallexm pveproxy[3006]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServe>
Mar 04 11:10:11 PM-00vallexm pveproxy[3007]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServe>
Mar 04 11:10:16 PM-00vallexm pveproxy[3008]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServe>
Mar 04 11:10:16 PM-00vallexm pveproxy[3009]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServe>
Mar 04 11:10:16 PM-00vallexm pveproxy[3010]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServe>
Click to expand...
That's probably the problem that causes several of the PVE services not starting properly. Is this is fresh install (via the installer or via Debian first?) and you did not change anything?
I have no personal experience with this error but it is not uncommon when searching the forum: https://forum.proxmox.com/search/67...t=post&c[child_nodes]=1&c[nodes][0]=16&o=date
 
leesteken said:
That's probably the problem that causes several of the PVE services not starting properly. Is this is fresh install (via the installer or via Debian first?) and you did not change anything?
I have no personal experience with this error but it is not uncommon when searching the forum: https://forum.proxmox.com/search/67...t=post&c[child_nodes]=1&c[nodes][0]=16&o=date
Click to expand...

This is a clean installation via the installer, I'll read about the error, thanks. It's sad that something doesn't work out of the box anymore (
 
I installed the old version of proxmox-ve_7.4-1.iso and everything worked right away, the web interface is available. I'm guessing there's some problem with the latest build.
 
I have the same problem and doubt for the message below:
HTML: 
/etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServe

After googling several articles I conclude it is most likely about
/etc/hosts

But how? How cloud I fix this by correct my /etc/hosts?
 
benxtong said:
Got it and Fixed. Really appreciate your indication.
Click to expand...

Thanks! Please leave a comment in the linked thread. I have seen this so many times, I would like to start counting - I submit Bugzilla reports based on this and the more users affected, the more likely things get fixed (with e.g. better error messages).
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom