I getting problem with Ubuntu repository on Ubuntu 16.04 and 18.04 droplets created in London. For droplets created in Frankfurt everything works out of box.
Does anyone experiencing this too?
# apt-get update
Ign:4 http://security.debian.org bionic/updates InRelease
Ign:1 http://lon1.mirrors.digitalocean.com/debian bionic InRelease
Err:6 http://security.debian.org bionic/updates Release
404 Not Found [IP: 151.101.60.204 80]
Ign:2 http://lon1.mirrors.digitalocean.com/debian bionic-updates InRelease
Ign:3 http://lon1.mirrors.digitalocean.com/debian bionic-backports InRelease
Err:5 http://lon1.mirrors.digitalocean.com/debian bionic Release
404 Not Found [IP: 5.101.111.50 80]
Err:7 http://lon1.mirrors.digitalocean.com/debian bionic-updates Release
404 Not Found [IP: 5.101.111.50 80]
Err:8 http://lon1.mirrors.digitalocean.com/debian bionic-backports Release
404 Not Found [IP: 5.101.111.50 80]
Hit:9 https://repos.sonar.digitalocean.com/apt main InRelease
Reading package lists... Done
E: The repository 'http://security.debian.org 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 'http://mirrors.digitalocean.com/debian bionic Release' no longer has 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://mirrors.digitalocean.com/debian bionic-updates Release' no longer has 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://mirrors.digitalocean.com/debian 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.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
To work around the issue I changed my sources to:
To work around the issue I changed my sources to:
I’m having a lot of issues in FrankFurt as well running installs through ansible on freshly created droplets with xenial ?
Same scripts were running perfectly yesterday :/ what’s going on here guys? I thought the premade builds were stable :/ appears they’re really not