I can't connect to web interface

Kujtim

Member
Oct 29, 2017
76
0
6
31
Im trying to connect but i can't i don't know why
Can anyone help me
Thank you
 
Hi Kujtim,

Please double check you are using https and are specifying the right port, i.e. https://<IP>:8006
Also, if you activated the firewall and try to connect from a remote host you need to make sure the appropriate rules are set, see https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_configuration_files subsection "Enabling the Firewall".
Otherwise, could you provide a bit more information? Can you reach the host in general? Was connecting to the web interface working in the past?

Best Regards,
Fabi
 
Hi Kujtim,

Please double check you are using https and are specifying the right port, i.e. https://<IP>:8006
Also, if you activated the firewall and try to connect from a remote host you need to make sure the appropriate rules are set, see https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_configuration_files subsection "Enabling the Firewall".
Otherwise, could you provide a bit more information? Can you reach the host in general? Was connecting to the web interface working in the past?

Best Regards,
Fabi
I didn't active any firewall 1 weeks ago i can connect without problem
Last night i want to connect to backup and i see i can't

Thank You
 
Could you connect via ssh as root and post the output of:
Code:
journalctl -b -u pveproxy.service
journalctl -b -u pvedaemon.service
and (please hide eventual public IP addresses appearing here):
Code:
ss -tulpen
 
Could you connect via ssh as root and post the output of:
Code:
journalctl -b -u pveproxy.service
journalctl -b -u pvedaemon.service
and (please hide eventual public IP addresses appearing here):
Code:
ss -tulpen
root@skynet-ks:~# journalctl -b -u pveproxy.service
-bash: journalctl: command not found
root@skynet-ks:~# journalctl -b -u pvedaemon.service
-bash: journalctl: command not found
root@skynet-ks:~# ss -tulpen
Netid State Recv-Q Send-Q Local Address:port Peer Address:port
udp UNCONN 0 0 *:111 *:* users:(("rpcbind",2200,6)) ino=11004 sk=ffff8801185c5bc0
udp UNCONN 0 0 10.10.100.27:123 *:* users:(("ntpd",2693,19)) ino=11760 sk=ffff88011c028440
udp UNCONN 0 0 127.0.0.1:123 *:* users:(("ntpd",2693,18)) ino=11759 sk=ffff88011c028080
udp UNCONN 0 0 *:123 *:* users:(("ntpd",2693,16)) ino=11683 sk=ffff88011dd70840
udp UNCONN 0 0 *:679 *:* users:(("rpcbind",2200,7)) ino=11007 sk=ffff88011c028bc0
udp UNCONN 0 0 127.0.0.1:697 *:* users:(("rpc.statd",2217,4)) ino=11061 sk=ffff880119269c00
udp UNCONN 0 0 *:52419 *:* users:(("rpc.statd",2217,7)) uid=105 ino=11068 sk=ffff88011dd70c00
udp UNCONN 0 0 :::111 :::* users:(("rpcbind",2200,9)) ino=11011 sk=ffff88011dd27ac0
udp UNCONN 0 0 fe80::7074:70ff:fef4:63df:123 : ::* users:(("ntpd",2693,26)) uid=101 ino=13822 sk=ffff8801187be980
udp UNCONN 0 0 fe80::b0e6:3ff:feaf:e38b:123 : ::* users:(("ntpd",2693,25)) uid=101 ino=13821 sk=ffff8801187bedc0
udp UNCONN 0 0 fe80::4469:ccff:fe38:e3ee:123 : ::* users:(("ntpd",2693,24)) uid=101 ino=13820 sk=ffff88011dd26e00
udp UNCONN 0 0 fe80::1:123 :::* users:(("ntpd",2693,23)) uid=101 ino=13819 sk=ffff88011dd26140
udp UNCONN 0 0 fe80::1aa9:5ff:fe1d:9907:123 : ::* users:(("ntpd",2693,21)) ino=11762 sk=ffff88011dd27240
udp UNCONN 0 0 ::1:123 :::* users:(("ntpd",2693,20)) ino=11761 sk=ffff8801187bf640
udp UNCONN 0 0 :::123 :::* users:(("ntpd",2693,17)) ino=11684 sk=ffff88011cecf6c0
udp UNCONN 0 0 :::38661 :::* users:(("rpc.statd",2217,9)) uid=105 ino=11076 sk=ffff88011cecfb00
udp UNCONN 0 0 :::679 :::* users:(("rpcbind",2200,10)) ino=11014 sk=ffff88011dd27680
tcp LISTEN 0 128 *:8006 *:* users:(("pveproxy worker",139289,7),("pveproxy worker",139288,7),("pveproxy wor ker",139287,7),("pveproxy",3065,7)) uid:33 ino:12889 sk:ffff88011e382840
tcp LISTEN 0 128 :::111 :::* users:(("rpcbind",2200,11)) ino:11015 sk:ffff88011c058840
tcp LISTEN 0 128 *:111 *:* users:(("rpcbind",2200,8)) ino:11008 sk:ffff88011cfaf7c0
tcp LISTEN 0 128 *:58962 *:* users:(("rpc.statd",2217,8)) uid:105 ino:11072 sk:ffff88011cf4f800
tcp LISTEN 0 128 :::38643 :::* users:(("rpc.statd",2217,10)) uid:105 ino:11080 sk:ffff8801187cd840
tcp LISTEN 0 128 127.0.0.1:85 *:* users:(("pvedaemon worke",3040,7),("pvedaemon worke",3039,7),("pvedaemon worke" ,3038,7),("pvedaemon",3037,7)) ino:12837 sk:ffff88011e382100
tcp LISTEN 0 128 :::22 :::* users:(("sshd",2757,4)) ino:11808 sk:ffff88011c058080
tcp LISTEN 0 128 *:22 *:* users:(("sshd",2757,3)) ino:11806 sk:ffff88011cfaf080
tcp LISTEN 0 128 *:3128 *:* users:(("spiceproxy work",3087,7),("spiceproxy",3086,7)) uid:33 ino:12935 sk:ff ff88011e77a800
tcp LISTEN 0 100 ::1:25 :::* users:(("master",2812,13)) ino:11961 sk:ffff88011e3f0840
tcp LISTEN 0 100 127.0.0.1:25 *:* users:(("master",2812,12)) ino:11959 sk:ffff88011d4f1880
 
From the output of 'ss' it seems that the services are running. But it is weird that you don't have 'journalctl'. What about:
Code:
systemctl status pveproxy.service
systemctl status pvedaemon.service
 
From the output of 'ss' it seems that the services are running. But it is weird that you don't have 'journalctl'. What about:
Code:
systemctl status pveproxy.service
systemctl status pvedaemon.service
root@skynet-ks:~# systemctl status pveproxy.service
-bash: systemctl: command not found
root@skynet-ks:~# systemctl status pvedaemon.service
-bash: systemctl: command not found
root@skynet-ks:~#
 
It seems like systemd is not installed (or at least not correctly). Please check your installation.
You can also run 'pvereport', but please post it as an attachment since the output is lengthy.
 
If you are running a very old version of PVE, not having systemd is to be expected.
Could you do 'uname -a' and 'pveversion -v' in that case?
 
If you are running a very old version of PVE, not having systemd is to be expected.
Could you do 'uname -a' and 'pveversion -v' in that case?

root@skynet-ks:~# uname -a
Linux skynet-ks 2.6.32-48-pve #1 SMP Fri Dec 23 10:22:54 CET 2016 x86_64 GNU/Linux
root@skynet-ks:~# pveversion -v
proxmox-ve-2.6.32: 3.4-185 (running kernel: 2.6.32-48-pve)
pve-manager: 3.4-16 (running version: 3.4-16/40ccc11c)
pve-kernel-2.6.32-39-pve: 2.6.32-157
pve-kernel-2.6.32-48-pve: 2.6.32-185
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-3
pve-cluster: 3.0-20
qemu-server: 3.4-9
pve-firmware: 1.1-6
libpve-common-perl: 3.0-27
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-35
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-28
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
root@skynet-ks:~#
 
I'm sorry I couldn't help you with your problem. Since your installation is very old, please consider upgrading (see this article and related ones).
 
Yes, it will be lost. Is there a special reason you need this version?

Another thing you can check using your browser is whether the network requests actually get to the server. For this you can use the Inspector in Firefox or the DevTools in Chromium. Just open the network monitor there and then try to connect to the web interface.
 

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!