Focus on cloud service provider activities
Notes on website operation and maintenance

Solution to the failure of updating official source by apt get in Debian system to replace 163 source

No matter which Linux VPS or server we choose, the first thing we need to do after logging into SSH remote is to update the source. This is required for both CentOS and Debian systems to ensure that the system source is the latest software version. Just now, when Lao Zuo was updating the source on a Debian system apt get update, he encountered an error message that the official source address 404 could not be obtained.

Err http://http.debian.net squeeze/main amd64 Packages 404 Not Found

 Solution to the failure of updating official source by apt get in Debian system to replace 163 source

It should be a source problem. The official source address of Debian cannot be obtained. Lao Zuo can change Alibaba source in CentOS system before. Please refer to this method( CentOS replaces Alibaba Cloud yum source to solve the problem of unable to update ), and the Debian system can do the same( Solve the problem that the Debian environment cannot update the source and replace the AliCloud image )Replace AliSource.

However, here's another way to use NetEase 163 source:

mv /etc/apt/sources.list /etc/apt/sources.list.bak && \
echo "deb http://mirrors.163.com/debian/ jessie main non-free contrib" >/etc/apt/sources.list && \
echo "deb http://mirrors.163.com/debian/ jessie-proposed-updates main non-free contrib" >>/etc/apt/sources.list && \
echo "deb-src http://mirrors.163.com/debian/ jessie main non-free contrib" >>/etc/apt/sources.list && \
echo "deb-src http://mirrors.163.com/debian/ jessie-proposed-updates main non-free contrib" >>/etc/apt/sources.list

Just throw it in.

 How to solve the problem of failing to update the official source by apt get in Debian system and replacing the 163 source - Page 2

After the execution, let's try apt get update - y.

 How to solve the problem of failing to update the official source of the Debian system apt get and replace the 163 source - Page 3

It seems that there is no major problem, but there is a small problem. The prompt "W: There is no public key available for the following key IDs" appears, which is not perfect and needs to be solved.

apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 7638D0442B90D010
apt-key adv --recv-keys --keyserver keyserver.ubuntu.com CBF8D6FD518E17E1

Execute according to different ID prompts. Then we update to see if there are any errors.

 How to solve the problem of failing to update the official source of the Debian system apt get and replace the 163 source - Page 4

It seems that this problem has been successfully solved.

Domain name host preferential information push QQ group: six hundred and twenty-seven million seven hundred and seventy-five thousand four hundred and seventy-seven Get preferential promotion from merchants.
Like( one )
Do not reprint without permission: Lao Zuo's Notes » Solution to the failure of updating official source by apt get in Debian system to replace 163 source


Scan the code to follow the official account

Get more news about webmaster circle!
Entrepreneurship, operation and new knowledge