PROXMOX VE 4.4 / SSH OK / No web access

[Sylvone]

Hello all,

I'm looking forward to find a solution to a strange issue.
I have installed Proxmox VE 4.4 on my HP microserver Gen8.
So far, no major issue, as I conducted the installation with direct acces to the server (no remot console,..).

After a few steps of configuration (adding repo, removing enterprise repos, upgrading), i rebooted and connected through the web client to Proxmox via Firefox. No issue.

But after rebooting IOT change some things in BIOS (especially diabling B120i card and enabling SATA AHCI), I a m unable to connect to Proxmox VE via web access.
I am able to connect via SSH, and to ping my server with its IP.
But using Firefox to connect to Proxmox returns me an error "connection failed", as if the server was not on the network...

I am thinking maybe there is a web service that is disabled, or something like that.
Because obviously my machine is connected to my LAN with the right IP, as i am able to ping it and to access it via SSH. Also I can see in my router that the machine is present in the LAN with the correct IP.
So I think it is not a networking issue, but rather a service that would not be loaded ?

I would appreciate any help, thanks !

Edit :
I checked the interface (nano /etc/network/interfaces), it is right configured.
I tried to restart pveproxy service, but it failed (Job for pveproxy.service failed. See 'systemctl status pveproxy.service' and 'journalctl -xn' for details.)

Looking at the logs, it mentions some problems :
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
Active: failed (Result: exit-code) since Sun 2017-07-02 10:30:38 CEST; 5min ago
Process: 1628 ExecStart=/usr/bin/pveproxy start (code=exited, status=2)

Jul 02 10:30:38 pve pveproxy[1628]: BEGIN failed--compilation aborted at /u...3.
Jul 02 10:30:38 pve pveproxy[1628]: Compilation failed in require at /usr/s...3.
Jul 02 10:30:38 pve pveproxy[1628]: BEGIN failed--compilation aborted at /u...3.
Jul 02 10:30:38 pve pveproxy[1628]: Compilation failed in require at /usr/s...5.
Jul 02 10:30:38 pve pveproxy[1628]: BEGIN failed--compilation aborted at /u...5.
Jul 02 10:30:38 pve pveproxy[1628]: Compilation failed in require at /usr/b...1.
Jul 02 10:30:38 pve pveproxy[1628]: BEGIN failed--compilation aborted at /u...1.
Jul 02 10:30:38 pve systemd[1]: pveproxy.service: control process exited, c...=2
Jul 02 10:30:38 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 02 10:30:38 pve systemd[1]: Unit pveproxy.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

 

[Sylvone]

pveversion -p returns this

Can't locate PVE/RESTEnvironment.pm in @INC (you may need to install the PVE::RESTEnvironment module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at /usr/share/perl5/PVE/RPCEnvironment.pm line 6.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/RPCEnvironment.pm line 6.
Compilation failed in require at /usr/share/perl5/PVE/API2/APT.pm line 20.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/APT.pm line 20.
Compilation failed in require at /usr/bin/pveversion line 7.
BEGIN failed--compilation aborted at /usr/bin/pveversion line 7.

After an update/upgrade/dist-upgrade, i now have :

root@pve:~# pveversion -v
proxmox-ve: 4.4-92 (running kernel: 4.4.67-1-pve)
pve-manager: 4.4-13 (running version: 4.4-13/7ea56165)
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.67-1-pve: 4.4.67-92
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-52
qemu-server: 4.0-110
pve-firmware: 1.1-11
libpve-common-perl: 4.0-95
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-100
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80

Moreover, service pveproxy restart returns now no error.
and when i check the status, everything seems fine :

● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
   Active: active (running) since Sun 2017-07-02 11:16:53 CEST; 57s ago
  Process: 1608 ExecStop=/usr/bin/pveproxy stop (code=exited, status=0/SUCCESS)
  Process: 1614 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
 Main PID: 1618 (pveproxy)
   CGroup: /system.slice/pveproxy.service
           ├─1618 pveproxy
           ├─1619 pveproxy worker
           ├─1620 pveproxy worker
           └─1621 pveproxy worker

Jul 02 11:16:53 pve pveproxy[1618]: starting server
Jul 02 11:16:53 pve pveproxy[1618]: starting 3 worker(s)
Jul 02 11:16:53 pve pveproxy[1618]: worker 1619 started
Jul 02 11:16:53 pve pveproxy[1618]: worker 1620 started
Jul 02 11:16:53 pve pveproxy[1618]: worker 1621 started
Jul 02 11:16:53 pve systemd[1]: Started PVE API Proxy Server.

 

[Sylvone]

Hourra !

Solution found ! It was a certificate issue.

So I just ran

pvecm updatecerts

And my web acces is now back !
Hope it may help someone else !