Since we did the instructions for Proxmox VE 3.4 initial installation, here is the change for Proxmox VE 4.0:
Initial Proxmox installer GUI tips:
Upon first boot:
1. Login via SSH/ console and get the right packages/ repos setup. Use the IP address set in the GUI installer. By default Proxmox will try to use the enterprise repos. To fix this first add the no subscription sources:
Then remove the enterprise source:
2. Update and upgrade
3. Reboot - I ran into an issue with ZFS RAID 1 after updating, ensure you can still boot the server!
I like to ensure that I have IPMI up for any server I am doing this with just to troubleshoot reboot issues.
4. Login to the web interface.
I hope that helps someone. Good chance it will be me in a week or two when I try this again
Initial Proxmox installer GUI tips:
- If you can, mirrored boot is a good idea. I have been using ZFS RAID 1 since Proxmox VE 3.4 and it works well. I would suggest not using UEFI boot and instead using legacy BIOS. If you are installing via IPMI, ensure the virtual media device does not say UEFI at the start.
- On the network settings screen on the installer pick something other than pve.x.x as your host name. If you leave defaults, it will get confusing later. Also set a static IP and remember your password.
- Ensure you will have a way to resolve hostnames in your setup. Proxmox likes this
Upon first boot:
1. Login via SSH/ console and get the right packages/ repos setup. Use the IP address set in the GUI installer. By default Proxmox will try to use the enterprise repos. To fix this first add the no subscription sources:
Code:
# nano /etc/apt/sources.list
add:
deb http://download.proxmox.com/debian jessie pve-no-subscription
Then remove the enterprise source:
Code:
# nano /etc/apt/sources.list.d/pve-enterprise.list
comment out (add a # symbol in front) of this line:
# deb https://enterprise.proxmox.com/debian jessie pve-enterprise
2. Update and upgrade
Code:
apt-get update && apt-get dist-upgrade -y
I like to ensure that I have IPMI up for any server I am doing this with just to troubleshoot reboot issues.
4. Login to the web interface.
I hope that helps someone. Good chance it will be me in a week or two when I try this again
Last edited: