ubuntu更新问题
版面规则
我们都知道新人的确很菜,也喜欢抱怨,并且带有浓厚的Windows习惯,但既然在这里询问,我们就应该有责任帮助他们解决问题,而不是直接泼冷水、简单的否定或发表对解决问题没有任何帮助的帖子。乐于分享,以人为本,这正是Ubuntu的精神所在。
我们都知道新人的确很菜,也喜欢抱怨,并且带有浓厚的Windows习惯,但既然在这里询问,我们就应该有责任帮助他们解决问题,而不是直接泼冷水、简单的否定或发表对解决问题没有任何帮助的帖子。乐于分享,以人为本,这正是Ubuntu的精神所在。
-
- 帖子: 3
- 注册时间: 2019-10-16 9:18
- 系统: win10
ubuntu更新问题
各位大侠有没有遇到这种情况,ubuntu18.04 无法更新,开始以为是源的问题,换了阿里源,163源,清华源都不行。结果看是没有对应的文件,网上说是ubuntu把这个版本移到了old-releases里了,官方的源也有试过,结果是一样的,也有试过再deb 后面加这个 [trusted=yes] ,但结果也是一样。论坛有没有大佬遇到这样问题解决了的方法啊。网上也搜过,各种方式也试过....只能来论坛问问了。
z@z:~$ sudo apt-get update
Ign:1 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic InRelease
Ign:2 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-updates InRelease
Ign:3 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-backports InRelease
Ign:4 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-security InRelease
Err:5 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic Release
Could not handshake: Error in the pull function. [IP: 218.104.71.170 443]
Err:6 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-updates Release
Could not handshake: Error in the pull function. [IP: 218.104.71.170 443]
Err:7 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-backports Release
Could not handshake: Error in the pull function. [IP: 218.104.71.170 443]
Err:8 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-security Release
Could not handshake: Error in the pull function. [IP: 218.104.71.170 443]
Ign:9 http://repo.zabbix.com/zabbix/4.0/ubuntu bionic InRelease
Err:10 http://repo.zabbix.com/zabbix/4.0/ubuntu bionic Release
SECURITY: URL redirect target contains control characters, rejecting. [IP: 162.243.159.138 80]
Reading package lists... Done
E: The repository 'https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic 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.
E: The repository 'https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-updates 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.
E: The repository 'https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-backports 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.
E: The repository 'https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-security 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.
E: The repository 'http://repo.zabbix.com/zabbix/4.0/ubuntu bionic 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.
z@z:~$ sudo apt-get update
Ign:1 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic InRelease
Ign:2 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-updates InRelease
Ign:3 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-backports InRelease
Ign:4 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-security InRelease
Err:5 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic Release
Could not handshake: Error in the pull function. [IP: 218.104.71.170 443]
Err:6 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-updates Release
Could not handshake: Error in the pull function. [IP: 218.104.71.170 443]
Err:7 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-backports Release
Could not handshake: Error in the pull function. [IP: 218.104.71.170 443]
Err:8 https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-security Release
Could not handshake: Error in the pull function. [IP: 218.104.71.170 443]
Ign:9 http://repo.zabbix.com/zabbix/4.0/ubuntu bionic InRelease
Err:10 http://repo.zabbix.com/zabbix/4.0/ubuntu bionic Release
SECURITY: URL redirect target contains control characters, rejecting. [IP: 162.243.159.138 80]
Reading package lists... Done
E: The repository 'https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic 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.
E: The repository 'https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-updates 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.
E: The repository 'https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-backports 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.
E: The repository 'https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu bionic-security 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.
E: The repository 'http://repo.zabbix.com/zabbix/4.0/ubuntu bionic 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.
- astolia
- 论坛版主
- 帖子: 6703
- 注册时间: 2008-09-18 13:11
Re: ubuntu更新问题
你看哪里说的?18.04支持周期长达10年,要移到old-releases也是2028年以后的事了
自己把源从
https://mirrors.ustc.edu.cn/ubuntu-old-releases/ubuntu
改成
https://mirrors.ustc.edu.cn/ubuntu
-
- 帖子: 3
- 注册时间: 2019-10-16 9:18
- 系统: win10
Re: ubuntu更新问题
都有试过,一样的,无法更新。
-
- 帖子: 3
- 注册时间: 2019-10-16 9:18
- 系统: win10
Re: ubuntu更新问题
deb https://mirrors.ustc.edu.cn/ubuntu bionic-security main restricted
deb-src https://mirrors.ustc.edu.cn/ubuntu bionic-security main restricted
deb https://mirrors.ustc.edu.cn/ubuntu bionic-security universe
deb-src https://mirrors.ustc.edu.cn/ubuntu bionic-security universe
deb https://mirrors.ustc.edu.cn/ubuntu bionic-security multiverse
deb-src https://mirrors.ustc.edu.cn/ubuntu bionic-security multiverse
换回来后,apt-get update 结果还是一样,请大佬指点。
deb-src https://mirrors.ustc.edu.cn/ubuntu bionic-security main restricted
deb https://mirrors.ustc.edu.cn/ubuntu bionic-security universe
deb-src https://mirrors.ustc.edu.cn/ubuntu bionic-security universe
deb https://mirrors.ustc.edu.cn/ubuntu bionic-security multiverse
deb-src https://mirrors.ustc.edu.cn/ubuntu bionic-security multiverse
换回来后,apt-get update 结果还是一样,请大佬指点。
- astolia
- 论坛版主
- 帖子: 6703
- 注册时间: 2008-09-18 13:11
Re: ubuntu更新问题
你要把路径改正确后的错误信息发上来啊
repo.zabbix.com这个源支持https,你把它改成https的
从这个看,我怀疑你的网络环境里有人尝试利用今年初爆出的漏洞CVE-2019-3462搞入侵,这种情况下你还敢加trusted=yes,真是在作死的路上一路狂奔,为各种黑客大开方便之门Err:10 http://repo.zabbix.com/zabbix/4.0/ubuntu bionic Release
SECURITY: URL redirect target contains control characters, rejecting. [IP: 162.243.159.138 80]
repo.zabbix.com这个源支持https,你把它改成https的
- 老铁没毛病
- 帖子: 5
- 注册时间: 2021-10-09 10:36
- 系统: ubuntu 18.04
Re: ubuntu更新问题
看下自己的source.list
deb https://mirrors.ustc.edu.cn/ubuntu/ bionic main restricted universe multiverse
deb-src https://mirrors.ustc.edu.cn/ubuntu/ bionic main restricted universe multiverse
deb https://mirrors.ustc.edu.cn/ubuntu/ bionic-security main restricted universe multiverse
deb-src https://mirrors.ustc.edu.cn/ubuntu/ bionic-security main restricted universe multiverse
deb https://mirrors.ustc.edu.cn/ubuntu/ bionic-updates main restricted universe multiverse
deb-src https://mirrors.ustc.edu.cn/ubuntu/ bionic-updates main restricted universe multiverse
deb https://mirrors.ustc.edu.cn/ubuntu/ bionic-backports main restricted universe multiverse
deb-src https://mirrors.ustc.edu.cn/ubuntu/ bionic-backports main restricted universe multiverse
## Not recommended
# deb https://mirrors.ustc.edu.cn/ubuntu/ bionic-proposed main restricted universe multiverse
# deb-src https://mirrors.ustc.edu.cn/ubuntu/ bionic-proposed main restricted universe multiverse
上面这个是ustc的 18.04的source.list,如果自己有加一些其他的源,比如ppa或者wine等,会比上面多一些
首先保证基本的source.list(ustc的sourcelist部分)能正常update,然后再加上自己新增的deb源正常update(比如ppa、wine、zabbix等)
1. 如果是ustc的deb报错,看是不是使用了http,一般http会因为非安全因素受限,一般http受限报错是下面这种
SECURITY: URL redirect target contains control characters, rejecting. [IP: 202.141.160.110 80]
将对应source.list里的http改成https就好了
如果改成https还不行,要看报错情况,如果是下面这种报错,可能是因为缺少ca-certificates包
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the
certificate verification. [IP: 101.6.15.130 443]
这种报错,可以从https://pkgs.org/download/ca-certificates根据自己的情况下载对应的deb文件然后安装,就可以了
2. 如果是新增的非ustc的deb报错,直接在source.list里注释掉就好了
比如你的source.list就新增了http://repo.zabbix.com/zabbix/4.0/ubuntu bionic InRelease这个,在source.list里先注释掉,根据第1步保证基本的deb能正常update,然后在加上你新增的这个,根据报错,看如何处理新增deb的报错
如astolia所说,repo.zabbix.com也支持https,不知道你改成https能否解决问题
3. 还有一种是新增的非ustc的deb虽然报错,但是在source.list里没有,这个可以到“软件和更新”---->“其他软件”里找到,然后手动勾掉就可以了
其他:
1. 网上说是ubuntu把这个版本移到了old-releases里了
这个一般是非LTS的ubuntu版本才会在超出一定时间后,移到其他路径下,导致找不到Release文件
不过你的http://repo.zabbix.com/zabbix/4.0/ubuntu也报同样的错误,这个和ubuntu没关系了,如astolia所说和这个没关系的
2. 待补充
deb https://mirrors.ustc.edu.cn/ubuntu/ bionic main restricted universe multiverse
deb-src https://mirrors.ustc.edu.cn/ubuntu/ bionic main restricted universe multiverse
deb https://mirrors.ustc.edu.cn/ubuntu/ bionic-security main restricted universe multiverse
deb-src https://mirrors.ustc.edu.cn/ubuntu/ bionic-security main restricted universe multiverse
deb https://mirrors.ustc.edu.cn/ubuntu/ bionic-updates main restricted universe multiverse
deb-src https://mirrors.ustc.edu.cn/ubuntu/ bionic-updates main restricted universe multiverse
deb https://mirrors.ustc.edu.cn/ubuntu/ bionic-backports main restricted universe multiverse
deb-src https://mirrors.ustc.edu.cn/ubuntu/ bionic-backports main restricted universe multiverse
## Not recommended
# deb https://mirrors.ustc.edu.cn/ubuntu/ bionic-proposed main restricted universe multiverse
# deb-src https://mirrors.ustc.edu.cn/ubuntu/ bionic-proposed main restricted universe multiverse
上面这个是ustc的 18.04的source.list,如果自己有加一些其他的源,比如ppa或者wine等,会比上面多一些
首先保证基本的source.list(ustc的sourcelist部分)能正常update,然后再加上自己新增的deb源正常update(比如ppa、wine、zabbix等)
1. 如果是ustc的deb报错,看是不是使用了http,一般http会因为非安全因素受限,一般http受限报错是下面这种
SECURITY: URL redirect target contains control characters, rejecting. [IP: 202.141.160.110 80]
将对应source.list里的http改成https就好了
如果改成https还不行,要看报错情况,如果是下面这种报错,可能是因为缺少ca-certificates包
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the
certificate verification. [IP: 101.6.15.130 443]
这种报错,可以从https://pkgs.org/download/ca-certificates根据自己的情况下载对应的deb文件然后安装,就可以了
2. 如果是新增的非ustc的deb报错,直接在source.list里注释掉就好了
比如你的source.list就新增了http://repo.zabbix.com/zabbix/4.0/ubuntu bionic InRelease这个,在source.list里先注释掉,根据第1步保证基本的deb能正常update,然后在加上你新增的这个,根据报错,看如何处理新增deb的报错
如astolia所说,repo.zabbix.com也支持https,不知道你改成https能否解决问题
3. 还有一种是新增的非ustc的deb虽然报错,但是在source.list里没有,这个可以到“软件和更新”---->“其他软件”里找到,然后手动勾掉就可以了
其他:
1. 网上说是ubuntu把这个版本移到了old-releases里了
这个一般是非LTS的ubuntu版本才会在超出一定时间后,移到其他路径下,导致找不到Release文件
不过你的http://repo.zabbix.com/zabbix/4.0/ubuntu也报同样的错误,这个和ubuntu没关系了,如astolia所说和这个没关系的
2. 待补充
- 老铁没毛病
- 帖子: 5
- 注册时间: 2021-10-09 10:36
- 系统: ubuntu 18.04
Re: ubuntu更新问题
新增第三方deb源,报错找不到Release文件的解决办法
1. ppa类型
如果使用http或者https始终找不到Release文件,那么需要找到服务器,查看对应的说明文档
具体步骤可以参考这个连接的解决方式https://blog.csdn.net/blongz/article/details/106164803
该链接的步骤为:找到报错的链接,然后打开链接找到服务器对应的网站上,寻找使用说明,根据对应的使用说明排查错误
1. ppa类型
如果使用http或者https始终找不到Release文件,那么需要找到服务器,查看对应的说明文档
具体步骤可以参考这个连接的解决方式https://blog.csdn.net/blongz/article/details/106164803
该链接的步骤为:找到报错的链接,然后打开链接找到服务器对应的网站上,寻找使用说明,根据对应的使用说明排查错误
上次由 老铁没毛病 在 2021-11-18 14:37,总共编辑 2 次。
- 老铁没毛病
- 帖子: 5
- 注册时间: 2021-10-09 10:36
- 系统: ubuntu 18.04
Re: ubuntu更新问题
2. ubuntu-cloud类型(无使用说明文档,网络限制http的情况)
我想安装ussuri,通过命令sudo add-apt-repository cloud-archive:ussuri新增了源
但是同样报错
忽略:1 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/ussuri InRelease
错误:2 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/ussuri Release
SECURITY: URL redirect target contains control characters, rejecting. [IP: 91.189.88.152 80]
正在读取软件包列表... 完成
E: 仓库 “http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/ussuri Release” 没有 Release 文件。
N: 无法安全地用该源进行更新,所以默认禁用该源。
N: 参见 apt-secure(8) 手册以了解仓库创建和用户配置方面的细节。
通过打开网址http://ubuntu-cloud.archive.canonical.com/发现对应路径下的Release文件是存在的,也就是说在本地配置正常,网络OK的情况下,我应该能正常连接到服务器上
但是因为该网站不同于repo.zabbix.com,不支持https,而我的网络任何源使用http都无法执行update(办公网络限制http)
综上,在网络http受限时,针对只支持http的源,我们只需要想办法切换到不被限制的网络(比如手机热点),就可以正常更新了
另外,网上针对找不到Release文件问题时,删除source.list.d目录下的对应文件的处理方法,等同于手动去除掉新增的第三方源,不是解决根因的办法
如何确认源所在的Release文件是否存在?
比如中科大USTC的源https://mirrors.ustc.edu.cn/ubuntu bionic-updates
手动打开https://mirrors.ustc.edu.cn/ubuntu,在该路径下如果存在对应的Release文件的话,应该存在如下的文件
https://mirrors.ustc.edu.cn/ubuntu/ dists/bionic-updates/InRelease
https://mirrors.ustc.edu.cn/ubuntu/ dists/bionic-updates/Release
https://mirrors.ustc.edu.cn/ubuntu/ dists/bionic-updates/Release.gpg
具体可查看https://mirrors.ustc.edu.cn/ubuntu/dists/bionic-updates/
如果新增的第三方源,比如我新增的ussuri,是否存在对应的Release文件
我只需要看下http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/bionic-updates目录下是否存在相关文件即可
我想安装ussuri,通过命令sudo add-apt-repository cloud-archive:ussuri新增了源
但是同样报错
忽略:1 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/ussuri InRelease
错误:2 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/ussuri Release
SECURITY: URL redirect target contains control characters, rejecting. [IP: 91.189.88.152 80]
正在读取软件包列表... 完成
E: 仓库 “http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/ussuri Release” 没有 Release 文件。
N: 无法安全地用该源进行更新,所以默认禁用该源。
N: 参见 apt-secure(8) 手册以了解仓库创建和用户配置方面的细节。
通过打开网址http://ubuntu-cloud.archive.canonical.com/发现对应路径下的Release文件是存在的,也就是说在本地配置正常,网络OK的情况下,我应该能正常连接到服务器上
但是因为该网站不同于repo.zabbix.com,不支持https,而我的网络任何源使用http都无法执行update(办公网络限制http)
综上,在网络http受限时,针对只支持http的源,我们只需要想办法切换到不被限制的网络(比如手机热点),就可以正常更新了
另外,网上针对找不到Release文件问题时,删除source.list.d目录下的对应文件的处理方法,等同于手动去除掉新增的第三方源,不是解决根因的办法
如何确认源所在的Release文件是否存在?
比如中科大USTC的源https://mirrors.ustc.edu.cn/ubuntu bionic-updates
手动打开https://mirrors.ustc.edu.cn/ubuntu,在该路径下如果存在对应的Release文件的话,应该存在如下的文件
https://mirrors.ustc.edu.cn/ubuntu/ dists/bionic-updates/InRelease
https://mirrors.ustc.edu.cn/ubuntu/ dists/bionic-updates/Release
https://mirrors.ustc.edu.cn/ubuntu/ dists/bionic-updates/Release.gpg
具体可查看https://mirrors.ustc.edu.cn/ubuntu/dists/bionic-updates/
如果新增的第三方源,比如我新增的ussuri,是否存在对应的Release文件
我只需要看下http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/bionic-updates目录下是否存在相关文件即可
- 老铁没毛病
- 帖子: 5
- 注册时间: 2021-10-09 10:36
- 系统: ubuntu 18.04
Re: ubuntu更新问题
3. 国外源类型(无法使用,报错与楼主一致)
错误:11 https://mirrors.ustc.edu.cn/ubuntu bionic-backports Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 202.141.160.110 443]
错误:12 https://mirrors.ustc.edu.cn/ubuntu bionic-security Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 202.141.160.110 443]
错误:13 https://archive.ubuntu.com/ubuntu bionic Release
Could not handshake: Error in the pull function. [IP: 91.189.88.142 443]
错误:14 https://archive.ubuntu.com/ubuntu bionic-updates Release
Could not handshake: Error in the pull function. [IP: 91.189.88.142 443]
如上加粗下划线所示,archive.ubuntu.com/ubuntu属于国外的源,我们无法访问服务器的,也无法使用该源更新
其实国内的源也一样,网络找不到,也会报同样的错误,具体为什么国内的源会找不到,可能是source.list的deb加的不对找不到对应的路径,要么服务器上压根就没有Release相关的文件
如astolia所说,你的ustc报错,是因为你source.list加的deb不正确
错误:11 https://mirrors.ustc.edu.cn/ubuntu bionic-backports Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 202.141.160.110 443]
错误:12 https://mirrors.ustc.edu.cn/ubuntu bionic-security Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 202.141.160.110 443]
错误:13 https://archive.ubuntu.com/ubuntu bionic Release
Could not handshake: Error in the pull function. [IP: 91.189.88.142 443]
错误:14 https://archive.ubuntu.com/ubuntu bionic-updates Release
Could not handshake: Error in the pull function. [IP: 91.189.88.142 443]
如上加粗下划线所示,archive.ubuntu.com/ubuntu属于国外的源,我们无法访问服务器的,也无法使用该源更新
其实国内的源也一样,网络找不到,也会报同样的错误,具体为什么国内的源会找不到,可能是source.list的deb加的不对找不到对应的路径,要么服务器上压根就没有Release相关的文件
如astolia所说,你的ustc报错,是因为你source.list加的deb不正确
- 老铁没毛病
- 帖子: 5
- 注册时间: 2021-10-09 10:36
- 系统: ubuntu 18.04
Re: ubuntu更新问题
清华/中科大等sourcelist基础deb报错
1. ca-certificates包版本过旧
既然有这个包,你直接执行sudo apt-get update install ca-certificates是可以成功的,但是实际未安装任何软件
举例,我的ubuntu为20.04,在source.list使用清华对应https的源时,报错
直接执行sudo apt-get update install ca-certificates成功,但是执行update命令仍然报错
从上面可以看到新安装了 0 个软件包,实际上ca-certificates版本太旧导致出了问题
这时候,应该到https://pkgs.org/download/ca-certificates下载缺少ca-certificates包
对应ubuntu20.04下有两个版本,我果断选择最新的ca-certificates_20210119~20.04.2_all.deb下载,因为我本地已经有ca-certificates(20210119~20.04.1)
点开对应的ca-certificates_20210119~20.04.2_all.deb之后,下拉找到如下链接
直接新网页打开如下链接或者使用wget,下载后,使用dpkg安装
1. ca-certificates包版本过旧
出现上面这种报错的情况还有一种就是ca-certificates包版本过旧,但是因为apt update无法使用,所以没法更新如果改成https还不行,要看报错情况,如果是下面这种报错,可能是因为缺少ca-certificates包
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the
certificate verification. [IP: 101.6.15.130 443]
这种报错,可以从https://pkgs.org/download/ca-certificates根据自己的情况下载对应的deb文件然后安装,就可以了
既然有这个包,你直接执行sudo apt-get update install ca-certificates是可以成功的,但是实际未安装任何软件
举例,我的ubuntu为20.04,在source.list使用清华对应https的源时,报错
代码: 全选
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the
certificate verification
代码: 全选
正在读取软件包列表... 完成
正在分析软件包的依赖关系树
正在读取状态信息... 完成
ca-certificates 已经是最新版 (20210119~20.04.1)。
升级了 0 个软件包,新安装了 0 个软件包,要卸载 0 个软件包,有 0 个软件包未被升级。
这时候,应该到https://pkgs.org/download/ca-certificates下载缺少ca-certificates包
对应ubuntu20.04下有两个版本,我果断选择最新的ca-certificates_20210119~20.04.2_all.deb下载,因为我本地已经有ca-certificates(20210119~20.04.1)
代码: 全选
ca-certificates_20210119~20.04.2_all.deb
ca-certificates_20190110ubuntu1_all.deb
代码: 全选
Binary Package http://ports.ubuntu.com/pool/main/c/ca-certificates/ca-certificates_20210119~20.04.2_all.deb