I'm upgrading a server from 3.4 to 4.0. I installed 4.0 an a new server and checked the Web UI working O.K. using the IP-address.
Copied my vzdump files over from old to new server and stopped the old one. Then I changed the name in /etc/hostname, /etc/hosts and /etc/postfix/main.cf, invoked newaliases and rebooted.
The server did change the name. I can easily access the UI using the IP address (https://144.76.xx.xxx:8006/#v1:0:=node/bulava:3:5:6::::), even though the browser complains that the certificate claims to be for "bulava.xxx.xx".
However if I try to access the UI using the url https://bulava.xxx.xx:8006 I get an empty response.
Something seems to be broken with the virtual hosts configuration, but I can't find it.
I grepped the new ("bulava") and the old ("tamy") name in /etc without results
Where are the web server config files now?
BTW here are the versions I use:
Copied my vzdump files over from old to new server and stopped the old one. Then I changed the name in /etc/hostname, /etc/hosts and /etc/postfix/main.cf, invoked newaliases and rebooted.
The server did change the name. I can easily access the UI using the IP address (https://144.76.xx.xxx:8006/#v1:0:=node/bulava:3:5:6::::), even though the browser complains that the certificate claims to be for "bulava.xxx.xx".
However if I try to access the UI using the url https://bulava.xxx.xx:8006 I get an empty response.
Something seems to be broken with the virtual hosts configuration, but I can't find it.
I grepped the new ("bulava") and the old ("tamy") name in /etc without results
Code:
root@bulava:/etc# grep -rHl bulava *
aliases.db
hostname
hosts
postfix/main.cf
pve/.version
pve/.rrd
pve/.clusterlog
pve/.members
root@bulava:/etc# grep -rHl tamy *
lvm/backup/pve
lvm/archive/pve_00000-1875040931.vg
pve/priv/authorized_keys
ssh/ssh_host_ecdsa_key.pub
ssh/ssh_host_rsa_key.pub
ssh/ssh_host_ed25519_key.pub
ssh/ssh_host_dsa_key.pubBTW here are the versions I use:
Code:
root@bulava:/etc# pveversion -v
proxmox-ve: 4.0-3 (running kernel: 3.19.8-1-pve)
pve-manager: 4.0-24 (running version: 4.0-24/946af136)
pve-kernel-3.19.8-1-pve: 3.19.8-3
lvm2: 2.02.116-pve1
corosync-pve: 2.3.4-2
libqb0: 0.17.1-3
pve-cluster: 4.0-14
qemu-server: 4.0-13
pve-firmware: 1.1-5
libpve-common-perl: 4.0-10
libpve-access-control: 4.0-5
libpve-storage-perl: 4.0-12
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.3-6
pve-container: 0.9-3
pve-firewall: 2.0-4
pve-ha-manager: 1.0-4
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2
lxc-pve: 1.1.2-1
lxcfs: 0.9-pve1
cgmanager: 0.37-pve1
Last edited:
Hell, because it's over a IP-KVM and virtual CDROM media ... will take forever again