Error: when running "sudo apt-get update" 'Origin' value from 'apt.vesta.hostingpanel.dev' to 'apt.myvestacp.com'

Post Reply
sparkzara
Posts: 22
Joined: Mon Jun 07, 2021 9:15 am

Hi,
i get a strange error when doing routine server update.

Code: Select all

Hit:1 http://mirrors.linode.com/debian buster InRelease
Hit:2 http://mirrors.linode.com/debian-security buster/updates InRelease
Hit:3 http://mirrors.linode.com/debian buster-updates InRelease
Hit:4 https://packages.sury.org/php buster InRelease
Get:5 http://apt.myvestacp.com/buster buster InRelease [2,296 B]
Hit:6 http://nginx.org/packages/debian buster InRelease
Reading package lists... Done
E: Repository 'http://apt.myvestacp.com/buster buster InRelease' changed its 'Origin' value from 'apt.vesta.hostingpanel.dev' to 'apt.myvestacp.com'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
is this something to do with recent myvestacp update ?
something to revert back or what should be done ?
User avatar
myVesta
Site Admin
Posts: 928
Joined: Fri Jun 19, 2020 9:59 am
Has thanked: 8 times
Been thanked: 6 times

"apt.vesta.hostingpanel.dev" was old apt address from the days when I didn't publically publish myVesta yet.
Yesterday I saw it's still written in apt repo, and I changed to "apt.myvestacp.com", which is official apt repo address.
Well, i didn't realized it will brake apt on servers.

I reverted back to "apt.vesta.hostingpanel.dev".
Should be fine now.

Thanks for notification about this.
Jpsciolli
Posts: 13
Joined: Sun Feb 21, 2021 6:54 pm

Hello,

I guess I´ve got something similar, can you please check it?

root@cp:/home/admin# apt-get update
Hit:1 http://mirrors.linode.com/debian buster InRelease
Hit:2 http://mirrors.linode.com/debian-security buster/updates InRelease
Hit:3 http://mirrors.linode.com/debian buster-updates InRelease
Hit:4 https://packages.sury.org/php buster InRelease
Hit:5 http://nginx.org/packages/debian buster InRelease
Get:6 http://apt.myvestacp.com/buster buster InRelease [2305 B]
Err:6 http://apt.myvestacp.com/buster buster InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 88807D4B2221338C
Fetched 2305 B in 1s (2848 B/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://apt.myvestacp.com/buster buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 88807D4B2221338C
W: Failed to fetch http://apt.myvestacp.com/buster/dists/buster/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 88807D4B2221338C
W: Some index files failed to download. They have been ignored, or old ones used instead.
User avatar
myVesta
Site Admin
Posts: 928
Joined: Fri Jun 19, 2020 9:59 am
Has thanked: 8 times
Been thanked: 6 times

Jpsciolli wrote: Sat Jul 24, 2021 3:05 am Hello,

I guess I´ve got something similar, can you please check it?

W: Failed to fetch http://apt.myvestacp.com/buster/dists/buster/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 88807D4B2221338C
Check out the following article -> signatures couldn't be verified, public key is not available NO_PUBKEY 88807D4B2221338C
Post Reply