[SOLVED] Can ping, can connect using SSH but can't connect to the GUI

M

myloukou

New Member
Feb 9, 2024
9
2
3
geek.lio.is
Hello, new to PVE here.

I just installed it and I can't connect to the GUI

I can ping the PVE, I can connect using SSH, but nothing happens when I try to connect to the GUI with the browser to https://<pveip>:8006.

Any help?

Thanks
 
Other than obligatory checks e.g. firewall inbetween, etc, you can start with checking if curl works:
Code: 
curl -sk https://$ip_address:8006

Further it might be helpful to post ip a here and tell us a bit more about the network setup, is this all local network? Static IP assigned to PVE cannot have IP conflict with e.g. DHCP handed out ones, etc.
 
  • Like
Reactions: myloukou and bbgeek17
Hello! Thank you for the fast responses

tempacc346235 said:
Other than obligatory checks e.g. firewall inbetween, etc, you can start with checking if curl works:
Code: 
curl -sk https://$ip_address:8006

Further it might be helpful to post ip a here and tell us a bit more about the network setup, is this all local network? Static IP assigned to PVE cannot have IP conflict with e.g. DHCP handed out ones, etc.
Click to expand...

I get nothing with that command.

20240208_233949.jpg

The IP is static (192.160.0.200) and there's no conflict.

The PVE is connected directly through ethernet to the router and my laptop with Windows pro 11 (the client) via WIFI to the same router.

I also tried the proxmox app with my android phone and I get this error

error.png

The port number changes every time I try.
 
Can you post:

Code: 
journalctl -u pveproxy

ip a

EDIT: Also, can you post history? I know you said it's a fresh install, but ... let's see. :) Feel free to redact as appropriate.
 
Last edited:
  • Like
Reactions: myloukou
Here you have:

Code: 
root@rinconlionet:~# journalctl -u pveproxy
Feb 08 22:17:43 rinconlionet systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Feb 08 22:17:43 rinconlionet pvecm[821]: ipcc_send_rec[1] failed: Connection refused
Feb 08 22:17:43 rinconlionet pvecm[821]: ipcc_send_rec[2] failed: Connection refused
Feb 08 22:17:43 rinconlionet pvecm[821]: ipcc_send_rec[3] failed: Connection refused
Feb 08 22:17:43 rinconlionet pvecm[821]: Unable to load access control list: Connection refused
Feb 08 22:17:44 rinconlionet pveproxy[825]: starting server
Feb 08 22:17:44 rinconlionet pveproxy[825]: starting 3 worker(s)
Feb 08 22:17:44 rinconlionet pveproxy[825]: worker 826 started
Feb 08 22:17:44 rinconlionet pveproxy[825]: worker 827 started
Feb 08 22:17:44 rinconlionet pveproxy[825]: worker 828 started
Feb 08 22:17:44 rinconlionet systemd[1]: Started pveproxy.service - PVE API Proxy Server.
Feb 08 22:17:44 rinconlionet pveproxy[826]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or k>
Feb 08 22:17:44 rinconlionet pveproxy[827]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or k>
Feb 08 22:17:44 rinconlionet pveproxy[828]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or k>
Feb 08 22:17:49 rinconlionet pveproxy[826]: worker exit
Feb 08 22:17:49 rinconlionet pveproxy[827]: worker exit
Feb 08 22:17:49 rinconlionet pveproxy[828]: worker exit
Feb 08 22:17:49 rinconlionet pveproxy[825]: worker 826 finished
Feb 08 22:17:49 rinconlionet pveproxy[825]: starting 1 worker(s)
Feb 08 22:17:49 rinconlionet pveproxy[825]: worker 828 finished
Feb 08 22:17:49 rinconlionet pveproxy[825]: worker 827 finished
Feb 08 22:17:49 rinconlionet pveproxy[825]: worker 837 started
Feb 08 22:17:49 rinconlionet pveproxy[837]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or k>
Feb 08 22:17:54 rinconlionet pveproxy[825]: starting 2 worker(s)
Feb 08 22:17:54 rinconlionet pveproxy[825]: worker 838 started
Feb 08 22:17:54 rinconlionet pveproxy[825]: worker 839 started
Feb 08 22:17:54 rinconlionet pveproxy[837]: worker exit
Feb 08 22:17:54 rinconlionet pveproxy[838]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or k>
Feb 08 22:17:54 rinconlionet pveproxy[839]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or k>

Code: 
root@rinconlionet:~# 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 noprefixroute
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 00:e0:4b:50:7b:07 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 00:e0:4b:50:7b:07 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.200/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::2e0:4bff:fe50:7b07/64 scope link
       valid_lft forever preferred_lft forever

Code: 
    1  ping 192.168.0.1
    2  ping 192.168.0.111
    3  curl -ks https://localhost:8006
    4  curl -ks https://192.168.0.200:8006
    5  ping 192.168.0.111
    6  hostname-i
    7  hostname -i
    8  ping 192.168.0.111
    9  ping --help
   10  ping 192.168.0.111 -O
   11  ping 192.168.0.111 -B
   12  xit
   13  exit
   14  hostname
   15  exit
   16  exit
   17  curl -sk https://$ip_address:8006
   18  curl -sk https://192.168.0.200:8006
   19  curl -sk https://192.168.0.200:8006
   20  exit
   21  journalctl -u pveproxy i 192.168.0.200
   22  journalctl -u pveproxy ip 192.168.0.200
   23  journalctl -u pveproxy
   24  journalctl -u pveproxy
   25  ip a
   26  history

Yes, it's a fresh install... since I was unable to connect with the GUI i reinstalled it a couple of times.
 
It says this:

Code: 
cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.0.200 rincon@lionet.com rincon@lionet

# 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
 
myloukou said:
Oh! I see!!

Don't know what is doing that @ in there!!

Thanks a lot!!
Click to expand...

I think it was populated by the installer, you might have mistakenly filled in an email into a field where just the hostname belongs or it was somehow not well derived one for the other.

I take it like the GUI works now. Have fun!

(Just so you know, even for later, the reason - the hostname of your machine in /etc/hostname and the resolution of the same to an IP according to /etc/hosts must match, you were missing that and so your PVE filesystem did not get mapped, which is why you had /etc/pve emtpy, which is why the proxy had no access to the certificate, which is ... why;)
 
  • Like
Reactions: myloukou
tempacc346235 said:
I think it was populated by the installer, you might have mistakenly filled in an email into a field where just the hostname belongs or it was somehow not well derived one for the other.

I take it like the GUI works now. Have fun!

(Just so you know, even for later, the reason - the hostname of your machine in /etc/hostname and the resolution of the same to an IP according to /etc/hosts must match, you were missing that and so your PVE filesystem did not get mapped, which is why you had /etc/pve emtpy, which is why the proxy had no access to the certificate, which is ... why;)
Click to expand...

Yes! It's all working now! Thanks a lot

Screenshot 2024-02-09 012502.png
 
  • Like
Reactions: esi_y
You must log in or register to reply here.
Top Bottom