pve-ssl.key not installed with new installation

Von Paul

New Member
Apr 29, 2016
12
1
3
48
Hello,

We have a new installation of 4.2 which appeared to install with no issues. However, we are not able to access the web interface. It was noticed that the pve-ssl.key and pve-ssl.pem were not created at any point. Understandably so, since we then noticed there was nothing created under /etc/pve/priv, other than an empty authorized keys directory. I did not perform this install, just assisting, so I am providing as much info as I could obtain. Does anyone have an idea as to what would cause these necessary directories and files to not be created during install?

Note this is a 4.2 install on top of Debian 8.5 using the following:

echo "deb http://download.proxmox.com/debian jessie pve-no-subscription" > /etc/apt/sources.list.d/pve-install-repo.list

apt-get install proxmox-ve ntp ssh postfix ksm-control-daemon open-iscsi systemd-sysv

After reviewing an older post (https://forum.proxmox.com/threads/web-interface-not-working-in-proxmox-3.14141/), we attempted running pvecm updatecerts, with the following results (expected I suppose since there is not key to generate the certs)

----------------------------------------------------------------
Error opening Private Key /etc/pve/priv/authkey.key
139662759704208:error:02001002:system library:fopen:No such file or directory:bss_file.c:398:fopen('/etc/pve/priv/authkey.key','r')
139662759704208:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:400:
unable to load Private Key
command 'openssl rsa -in /etc/pve/priv/authkey.key -pubout -out /etc/pve/authkey.pub' failed: exit code 1
----------------------------------------------------------------

There is no cluster config at this time. The hostname and IP configurations were verified. The server initially obtained its NW information via DHCP, then was statically set.

Any help would be much appreciated! Please let me know if I can provide any further information.

Cheers,
Von
 
  • Like
Reactions: gvalverde
Same problem here. Have been installing multiple instances, this one failed just some minutes ago while installing, everything began to fail at this point
Code:
Setting up pve-cluster (4.0-41) ...
Error opening Private Key /etc/pve/priv/authkey.key
139874600175248:error:02001002:system library:fopen:No such file or directory:bss_file.c:398:fopen('/etc/pve/priv/authkey.key','r')
139874600175248:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:400:
unable to load Private Key
command 'openssl rsa -in /etc/pve/priv/authkey.key -pubout -out /etc/pve/authkey.pub' failed: exit code 1
dpkg: error processing package pve-cluster (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of libpve-access-control:
libpve-access-control depends on pve-cluster; however:
  Package pve-cluster is not configured yet.

dpkg: error processing package libpve-access-control (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of librados2-perl:
librados2-perl depends on libpve-access-control; however:
  Package libpve-access-control is not configured yet.

And it goes on and on..with the dpkg error, and at the end:
Code:
Errors were encountered while processing:
pve-cluster
libpve-access-control
librados2-perl
pve-firewall
pve-ha-manager
qemu-server
pve-container
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
 
Last edited:
bug fix is already on pve-devel, sorry for not catching this earlier..
 
>bug fix is already on pve-devel, sorry for not catching this earlier..
Any idea long will it take to be merged into the stable branch? Will a reinstall be needed?
 
same problem here.
i have created new key with:
pvecm keygen /etc/pve/priv/authkey.key
and now i can install all packages
 
WebGUI now works but can't login. Any input on this?

in /var/log/daemon.log:
Jun 14 15:39:41 proxmox pvedaemon[18182]: ipcc_send_rec failed: Transport endpoint is not connected
Jun 14 15:39:41 proxmox pvedaemon[18182]: authentication failure; rhost=::ffff:31.17.187.39 user=root@pam msg=RSA.xs:178: OpenSSL error: no start line at /usr/share/perl5/PVE/AccessControl.pm line 125.

I'm not sure if this way with manually cert creation is correct.
 
Does the fix require a reinstall; or will running upgrade or dist-upgrade work? Anyone tried yet?
 
Update: apt-get upgrade resolved the issue with the release of the fix...no reinstall performed. Another installation the following day on a different server did not have the issue.
 

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!