Super short version, is there a specific repo/set of repos for Ubuntu 24.04? Ran into some errors with the Debian instructions, mostly regarding the "Noble" codename for my OS and (possibly?) the lack of appropriate certificates for the bookworm, bookworm-updates, and bookworm-security repos. Will fully understand if it simply doesnt work on Ubuntu, and I perhaps misunderstood the "Debian Based" part of the instructions.
Context/steps taken so far: First time user of Proxmox Backup Server, and trying to dive in the deep end a bit as I already have several Proxmox Virtual Environment nodes running in my homelab, and some of them back up to an existing NAS. Rather than provision new hardware (or wipe the NAS and install PBS), I have decided to try to install PBS on top of Ubuntu, as it is a debian based release. To ensure I have ironed out any issues, I am starting first with installing PBS on an Ubuntu 24.04 Virtual Machine. I am attempting to follow the instructions located here: https://pbs.proxmox.com/docs/installation.html#install-pbs-on-debian.
The only oddity seems to have been when I followed the instructions for setting up the debian package repos. I set up the /etc/apt/sources.list with the following:
You will note I missed the Bookworm, Bookworm-updates, and bookworm-security repos, as I did not fully recognise why this No-Subscription section was different in its listing of all 4 repos. Other instructions on that page only reference the PBS repo, and so to start thats the only repo I grabbed.
Attempting to install immediately left me with errors about not having the correct cert, so as the page instructed (after I read a bit more carefully) I ran the following (and the MD5 checksum) and confirmed the cert was the "correct" certificate.
From there, did a quick apt update, upgrade, and then install of proxmox-backup-server
Which worked beautifully. I had to set a password on my root account, which previously didn't have one but then I was able to log in without issue. I immediately explored around, and noticed the updates and repositories section was throwing an error, which I took to mean that I had not added the appropriate set of repositories. I added the other repositories to my /etc/apt/sources.list file as the no-subscription instructions seemed to indicate I should:
but then when I ran apt update, I started getting errors about not having the appropriate certificates. After noting that, I briefly experimented with grabbing the repositories and cert rom the Proxmox Virtual Environment wiki, as I noticed the repositories were extremely similar (only differing in a couple of the URLs starting with FTP) to no avail.
Current state is that PBS seems to work just fine, except for the updates and repositories, which are showing an error about codename Noble (Canonical's codename for this ubuntu release, IIRC) not being a valid debian codename in the front end, and the awkard errors now thrown when I attempt to update using the bookworm repos.
Frontend:
SSH when running apt update:
Without any mechanism to keep it up to date I am a bit nervous to install it on my homelab NAS (no critical data, but to be honest its running a raid5 on some SMR drives and its slow as anything to rebuild the array) for fear of having to remake it. If I do end up bricking things, I do plan to explore the hardware raid I didn't know my motherboard had when I first set up the NAS, so the new iteration may at least be a touch easier to work with.
Apologies in advance if I have missed a thread that contains the answer for this already - I did some basic searches but did not find what I was looking for. The closest thread seemed to be about a 2023 issue regarding installing the PBS client on Ubuntu 22.04, and some library/dependency that needed to be rolled back to an older version to get PBS client to behave as expected.
Quick edit to avoid a potential tangent, I do not plan to have PBS storing the backups on the raid array used for the NAS, but instead to a specific SSD separate from the array and OS drive. I just wanted to use the same server so all my network storage would be in "one spot".
Context/steps taken so far: First time user of Proxmox Backup Server, and trying to dive in the deep end a bit as I already have several Proxmox Virtual Environment nodes running in my homelab, and some of them back up to an existing NAS. Rather than provision new hardware (or wipe the NAS and install PBS), I have decided to try to install PBS on top of Ubuntu, as it is a debian based release. To ensure I have ironed out any issues, I am starting first with installing PBS on an Ubuntu 24.04 Virtual Machine. I am attempting to follow the instructions located here: https://pbs.proxmox.com/docs/installation.html#install-pbs-on-debian.
The only oddity seems to have been when I followed the instructions for setting up the debian package repos. I set up the /etc/apt/sources.list with the following:
Code:
# Ubuntu sources have moved to /etc/apt/sources.list.d/ubuntu.sources
# Proxmox Backup Server pbs-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pbs bookworm pbs-no-subscriptionYou will note I missed the Bookworm, Bookworm-updates, and bookworm-security repos, as I did not fully recognise why this No-Subscription section was different in its listing of all 4 repos. Other instructions on that page only reference the PBS repo, and so to start thats the only repo I grabbed.
Attempting to install immediately left me with errors about not having the correct cert, so as the page instructed (after I read a bit more carefully) I ran the following (and the MD5 checksum) and confirmed the cert was the "correct" certificate.
Code:
wget https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg -O /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg
md5sum /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpgFrom there, did a quick apt update, upgrade, and then install of proxmox-backup-server
Code:
sudo apt update && sudo apt upgrade -y
sudo apt install proxmox-backup-serverWhich worked beautifully. I had to set a password on my root account, which previously didn't have one but then I was able to log in without issue. I immediately explored around, and noticed the updates and repositories section was throwing an error, which I took to mean that I had not added the appropriate set of repositories. I added the other repositories to my /etc/apt/sources.list file as the no-subscription instructions seemed to indicate I should:
Code:
deb http://deb.debian.org/debian bookworm main contrib
deb http://deb.debian.org/debian bookworm-updates main contrib
# Proxmox Backup Server pbs-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pbs bookworm pbs-no-subscription
# security updates
deb http://security.debian.org/debian-security bookworm-security main contribbut then when I ran apt update, I started getting errors about not having the appropriate certificates. After noting that, I briefly experimented with grabbing the repositories and cert rom the Proxmox Virtual Environment wiki, as I noticed the repositories were extremely similar (only differing in a couple of the URLs starting with FTP) to no avail.
Current state is that PBS seems to work just fine, except for the updates and repositories, which are showing an error about codename Noble (Canonical's codename for this ubuntu release, IIRC) not being a valid debian codename in the front end, and the awkard errors now thrown when I attempt to update using the bookworm repos.
Frontend:
SSH when running apt update:
Code:
sudo apt update && sudo apt upgrade -y
Get:1 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:2 http://ftp.debian.org/debian bookworm InRelease [151 kB]
Get:3 http://ftp.debian.org/debian bookworm-updates InRelease [55.4 kB]
Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease
Err:1 http://security.debian.org/debian-security bookworm-security InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 54404762BBB6E853 NO_PUBKEY BDE6D2B9216EC7A8
Hit:5 http://download.proxmox.com/debian/pbs bookworm InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu noble InRelease
Err:7 https://enterprise.proxmox.com/debian/pbs bookworm InRelease
401 Unauthorized [IP: 66.70.154.82 443]
Get:8 http://us.archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]
Err:2 http://ftp.debian.org/debian bookworm InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY F8D2585B8783D481
Hit:9 http://us.archive.ubuntu.com/ubuntu noble-backports InRelease
Err:3 http://ftp.debian.org/debian bookworm-updates InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131
Reading package lists... Done
W: GPG error: http://security.debian.org/debian-security bookworm-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 54404762BBB6E853 NO_PUBKEY BDE6D2B9216EC7A8
E: The repository 'http://security.debian.org/debian-security bookworm-security InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://enterprise.proxmox.com/debian/pbs/dists/bookworm/InRelease 401 Unauthorized [IP: 66.70.154.82 443]
E: The repository 'https://enterprise.proxmox.com/debian/pbs bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://ftp.debian.org/debian bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY F8D2585B8783D481
E: The repository 'http://ftp.debian.org/debian bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://ftp.debian.org/debian bookworm-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131
E: The repository 'http://ftp.debian.org/debian bookworm-updates InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.Without any mechanism to keep it up to date I am a bit nervous to install it on my homelab NAS (no critical data, but to be honest its running a raid5 on some SMR drives and its slow as anything to rebuild the array) for fear of having to remake it. If I do end up bricking things, I do plan to explore the hardware raid I didn't know my motherboard had when I first set up the NAS, so the new iteration may at least be a touch easier to work with.
Apologies in advance if I have missed a thread that contains the answer for this already - I did some basic searches but did not find what I was looking for. The closest thread seemed to be about a 2023 issue regarding installing the PBS client on Ubuntu 22.04, and some library/dependency that needed to be rolled back to an older version to get PBS client to behave as expected.
Quick edit to avoid a potential tangent, I do not plan to have PBS storing the backups on the raid array used for the NAS, but instead to a specific SSD separate from the array and OS drive. I just wanted to use the same server so all my network storage would be in "one spot".
Last edited:
