SYSTEM INFORMATION
OS type and version
Ubuntu Jammy
Webmin version
2.1111
Virtualmin version
7.10.0-gpl-1
Webserver version
Apache 2.4.62-1
apt-get update fails with NO_PUBKEY 3E570892B9A0B8B7
Yes, I have run, rerun, and re re re re re run virtualmin setup-repos
It’s not related with virtualmin. It might be the Server ISO which have a configuration problem.
Did you contacted the hosting Support ? What did they reply ?
It is, in fact, a Virtualmin problem, since it’s Virtualmin’s key.
ID10T
September 9, 2024, 7:29pm
4
There are different repos. Can you show us the output of the commands so we know for sure which repo is failing?
root@main:~# apt-get update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Get:2 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:3 http://deb.debian.org/debian-security bullseye-security InRelease
Hit:4 https://download.docker.com/linux/debian bullseye InRelease
Hit:5 https://software.virtualmin.com/vm/7/gpl/apt virtualmin InRelease
Get:6 https://packages.sury.org/php bullseye InRelease [7,551 B]
Get:7 https://packages.sury.org/php bullseye/main amd64 Packages [252 kB]
Fetched 303 kB in 7s (44.4 kB/s)
Reading package lists... Done
root@main:~# virtualmin setup-repos
Setting up Virtualmin software repositories ..
..done
Get:10 [https://software.virtualmin.com/vm/7/gpl/apt](https://software.virtualmin.com/vm/7/gpl/apt) virtualmin InRelease [10.7 kB]
Err:10 [https://software.virtualmin.com/vm/7/gpl/apt](https://software.virtualmin.com/vm/7/gpl/apt) virtualmin InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3E570892B9A0B8B7
ID10T
September 9, 2024, 7:55pm
6
Err:10 [https://software.virtualmin.com/vm/7/gpl/apt](https://software.virtualmin.com/vm/7/gpl/apt) virtualmin InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3E570892B9A0B8B7
My output is:
I mean, that’s great for you, but it doesn’t actually help me at all.
Steini
September 9, 2024, 9:39pm
8
As I’ve already said, I have done that. Repeatedly. With no change.
ID10T
September 9, 2024, 9:57pm
10
It was kind of a summary for the staff since I think that kinda distills the essence of the problem.
Keys are @Joe or @Ilia ? Not sure why the setup command didn’t fix it. I re-ran apt-get update afterwards and it still worked for me.
How long since you done the original install?
You could try using the setup switch on the latest script. I have no idea if it makes a difference.
sudo sh -c "$(curl -fsSL https://software.virtualmin.com/gpl/scripts/virtualmin-install.sh)" -- --setup
make sure you use the setup switch, don’t run otherwise.
ID10T
September 9, 2024, 10:33pm
12
It seems when I ran the command earlier my key was updated.
root@main:/etc/apt/sources.list.d# ll /usr/share/keyrings/debian-virtualmin-7.gpg
-rw-r--r-- 1 root root 2313 Sep 9 15:26 /usr/share/keyrings/debian-virtualmin-7.gpg
Years. Possibly a decade.
I also did try that invocation. It did not fix the issue.
/m
Joe
September 9, 2024, 10:44pm
14
Ah, if it’s that old, you probably have original sources that the setup doesn’t even know how to find.
Just remove the old Virtualmin sources. They’d be in /etc/apt/sources.list probably?
Joe looking at the github there is a force switch, does that do anything useful?
Joe
September 9, 2024, 10:55pm
16
That’s an Ilia change. I’m not sure what it does without looking, and I can’t look at the moment.
Ilia
September 10, 2024, 10:01am
17
No, it doesn’t. It’s redundant. I’ll go ahead and remove it.
There are no other virtualmin sources in either sources.list or sources.list.d. Only the current one that’s added by an attempt to use setup-repos
Joe
September 10, 2024, 6:05pm
19
What sources exactly are being used? (Don’t include serial/key, if you have Pro repos configured and the serial:key is in the sources file.)
Get:10 https://software.virtualmin.com/vm/7/gpl/apt virtualmin InRelease [10.7 kB]
Err:10 https://software.virtualmin.com/vm/7/gpl/apt virtualmin InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 3E570892B9A0B8B7