Skip to content

How to Update Proxmox VE When “You Do Not Have A Valid Subscription”

If you have recently dove into the Proxmox VE world, your mind is probably blowing chunks.  Proxmox gives you the unmatched ability to run hypervisor-like Virtual Machines, as well as containers, side by side with High Availability.  It’s an amazing virtualization platform and if you haven’t tried it out yet I highly recommend you do so.  After installing Proxmox 4.2 on one of my lab servers, I found the need to update it and I wasn’t about to pay for an Enterprise Subscription for my home lab.


How to update Proxmox when “You do not have a valid subscription for this server, please visit to get a list of available options” and keep you Proxmox server updated!”

There are a few steps involved and they go something like this:

  1. Disable the enterprise repository that is configured by default
  2. Add the no-subscription repository
  3. Update apt so it knows what can be updated
  4. Use apt to upgrade any packages
  5. Upgrade the entire distribution, using apt, of course

First, lets disable the enterprise repository.  You can’t run apt-get update by default without a subscription, you will get an error.  So, lets comment out that repo so it isn’t checked.  Go ahead and putty / ssh / console into your Proxmox server, and run the following command:

sed -i.bak 's|deb jessie pve-enterprise|\# deb jessie pve-enterprise|' /etc/apt/sources.list.d/pve-enterprise.list



Now, we need to add the no-subscription repo to /etc/apt/sources.list.d/pve-no-sub.list

#  echo "deb jessie pve-no-subscription" > /etc/apt/sources.list.d/pve-no-sub.list

If you want to know more about the repo we just added, head on over to




Now, it’s just a matter of running apt-get update and apt-get upgrade, list like you would on any Debian based Linux distribution.  So, first run an update.

#  apt-get update





After that finishes, you <strong>shouldn’t get any errors</strong> such as unable to download.  Now we will run <strong>apt-get upgrade</strong> to upgrade all packages.

#  apt-get upgrade

Select “Y” and hit enter, then it will start download and installing all package updates available.




Once the upgrade is complete, go ahead and reboot your Proxmox VE server.

#  shutdown -r now




All done!  Your Proxmox server is now up-to-date and in the future, you can just run apt-get update & apt-get upgrade to make sure all of your packages are current.  If you have any questions, feel free to ask in the comments below.  Thanks and have a great day!

7 thoughts on “How to Update Proxmox VE When “You Do Not Have A Valid Subscription”

  1. Ovan says:

    Would it be a problem if i updating my proxmox without subscription.?
    there are several working vps inside my proxmox


    • Mike Smith says:

      No problem at all. I have updated many times, without a subscription, while having VM’s deployed. Depending on what updates are installed, you might need to reboot the host server, and there fore your virtual machines as well, but aside from that there’s little risk.

  2. vl1969 says:

    FYI: I am not sure but with 4.3 , once you have the no subscription source file in place you can do refresh and upgrade from the web UI. it give you “no subscription” error but still does the upgrade.

  3. Pingback: Update ProxMox tanpa subscription – life.log

  4. Joe Bitcoin says:

    I found out that you should use instead…
    apt-get dist-upgrade

    Otherwise pve-manager broke for me. Glad my system wasn’t in production when I had to hunt that gem down!

  5. k0d3g3ar says:

    One thing that you neglected to mention is that if you have a cluster of servers, all servers must be running the same PM version, so first be sure to deal with the cluster (e.g. remove nodes from the cluster) before doing the upgrade and then re-connect them back once done.

  6. Richard Lloyd says:

    What I usually do on an upgrade of a Proxmox cluster is live migrate away all the VMs running on the first node that I want to update. Because you are going to need a reboot as part of the upgrade, you shouldn’t be running any VMs at all on the node to be upgraded. I then do the Proxmox upgrade (including a reboot) and then attempt a live migrate of the least important VM that was migrated away (ideally a test VM) back onto the upgraded node.

    It’s at this point that I’ve often hit a problem – live migration back often doesn’t work to the newer release, even for minor updates! It does appear that this critical functionality (being able to at least live migrate backwards and forwards between the last two Proxmox releases) is not tested on each release by the developers 🙁 I end up having to do an offline migrate, which is downtime for each VM – something you’re supposed to avoid at all costs in a clustered setup.


Leave a Reply