Interesting. I typed the IP that gave the 404 into my browser, and it came up with an invalid certificate. It's registered with lets encrypt. chrome says the cert's common name isn't valid. I bet our browser sessions are getting a different server than the server your bacula instance is running on. or we're getting a different cert for some reason.
I tried to just go to http instead of https, and my browser redirected to https. still, I think this is a https error. if you request the packages via http I bet the problem will go away. Regards, Robert Gerber 402-237-8692 r...@craeon.net On Wed, Oct 26, 2022 at 12:46 PM Neil Balchin <n...@neilandjo.com> wrote: > I can’t seem to access the Community binaries to update my now out of date > ubuntu bacula install. > > > Here’s what I’ve done: > > Registered for community access > Received mail with access-keys > > Downloaded and added gpg key files using > > wget > https://www.bacula.org/downloads/Bacula-4096-Distribution-Verification-key.asc > apt-key add Bacula-4096-Distribution-Verification-key.asc > > My output of apt-key list shows : > > /etc/apt/trusted.gpg > -------------------- > pub rsa4096 2018-09-03 [SC] > 5235 F5B6 68D8 1DB6 1704 A82D C0BE 2A5F E9DF 3643 > uid [ unknown] Bacula 4096 Distribution Verification Key ( > www.bacula.org) <k...@bacula.org> > sub rsa4096 2018-09-03 [E] > > /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg > ------------------------------------------------------ > pub rsa4096 2012-05-11 [SC] > 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 > uid [ unknown] Ubuntu Archive Automatic Signing Key (2012) < > ftpmas...@ubuntu.com> > > /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg > ------------------------------------------------------ > pub rsa4096 2012-05-11 [SC] > 8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092 > uid [ unknown] Ubuntu CD Image Automatic Signing Key (2012) < > cdim...@ubuntu.com> > > /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg > ------------------------------------------------------ > pub rsa4096 2018-09-17 [SC] > F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B C93C > uid [ unknown] Ubuntu Archive Automatic Signing Key (2018) < > ftpmas...@ubuntu.com> > > > Created new file at /etc/apt/sources.list.d/. Called bacula-community.list > > Here’s my deb line. (I’ve x’d out my access-keys, yes I’m sure they are > accurate I can paste this link into a web browser and I see the files) > > *#Bacula Community* > deb* [arch=amd64] **https://www.bacula.org/packages/xxxxxxxxxxxxx/debs/9.6.7 > <https://www.bacula.org/packages/xxxxxxxxxxxxx/debs/9.6.7>** focal** main* > > > When I run. apt-get update > > That’s when I get the 404 error > > > root@bacula:/tmp# apt-get update > Hit:1 http://ca.archive.ubuntu.com/ubuntu focal InRelease > Hit:2 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease > > Hit:3 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease > > Hit:4 http://ca.archive.ubuntu.com/ubuntu focal-security InRelease > > Ign:6 https://www.bacula.org/packages/xxxxxxxxxxxxx/debs/9.6.7 focal > InRelease > Hit:5 https://www.bacula.org/downloads/baculum/stable/ubuntu focal > InRelease > Err:7 https://www.bacula.org/packages/xxxxxxxxxxxxx/debs/9.6.7 focal > Release > 404 Not Found [IP: 94.103.98.87 443] > Reading package lists... Done > E: The repository 'https://www.bacula.org/packages/xxxxxxxxxxxxx/debs/9.6.7 > focal Release' does not have a Release file. > 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.1 > > If I type the deb url into a web browser, I get a perfect directory > listing > > > > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
