APT update problems and how to manage sources.list
by axolinx from LinuxQuestions.org on (#5BJRS)
I have 2 VPS on the same host provider.
Server 1 and Server 2 as seen in the screenshot below.
Server 1 has a nextcloud installation and i have previously been playing with certboot on it to issue the SSLertificates.
Server 2 on the right side, is a vanilla ubuntu 20.04 with nothing on it that i will be using to do experiments with and learning purposes.
So running "apt update" on server 1 fails with an error
server 2 updates without problems.
Both source.list files are very similar with almost the same repository servers.
I see there is a switch to force the updates anyway, but i am more interested in understanding why this happens being that the servers are very identical, and what causes these kind of problems, how to fix the repository files properly?
Will this error just go away if i force the update once or you have to hack into the system to make it permanent every time you encounter these issues?
Screenshot:
https://prnt.sc/w19ogh
Thank you guys
Server 1 and Server 2 as seen in the screenshot below.
Server 1 has a nextcloud installation and i have previously been playing with certboot on it to issue the SSLertificates.
Server 2 on the right side, is a vanilla ubuntu 20.04 with nothing on it that i will be using to do experiments with and learning purposes.
So running "apt update" on server 1 fails with an error
server 2 updates without problems.
Both source.list files are very similar with almost the same repository servers.
I see there is a switch to force the updates anyway, but i am more interested in understanding why this happens being that the servers are very identical, and what causes these kind of problems, how to fix the repository files properly?
Will this error just go away if i force the update once or you have to hack into the system to make it permanent every time you encounter these issues?
Screenshot:
https://prnt.sc/w19ogh
Thank you guys