Report this

What is the reason for this report?

Ubuntu 18.04 droplet - can't TLS handshake with https://repos.insights.digitalocean.com

Posted on July 24, 2020

Hi,

I’m trying to ‘apt update’ and receive the following error. This is new, this has not been an issue for the life of my droplet (well over a year).

Hit:1 http://mirrors.digitalocean.com/ubuntu bionic InRelease
Hit:2 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease
Hit:3 http://mirrors.digitalocean.com/ubuntu bionic-backports InRelease
Hit:4 https://deb.nodesource.com/node_13.x bionic InRelease
Ign:5 https://repos.insights.digitalocean.com/apt/do-agent main InRelease
Hit:6 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease
Hit:7 http://security.ubuntu.com/ubuntu bionic-security InRelease
Err:8 https://repos.insights.digitalocean.com/apt/do-agent main Release
  Could not handshake: The TLS connection was non-properly terminated. [IP: 199.59.242.154 443]
Hit:9 http://ppa.launchpad.net/costamagnagianfranco/borgbackup/ubuntu bionic InRelease
Hit:10 http://ppa.launchpad.net/dosemu2/ppa/ubuntu bionic InRelease
Reading package lists... Done
E: The repository 'https://repos.insights.digitalocean.com/apt/do-agent main 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.

I did use netstat to discover what appeared to be a Chinese IP address actively ssh’d into my box. I rebooted the box but still can’t connect to https://repos.insights.digitalocean.com - I can connect fine from home so this is localized to my droplet.

Was something potentially changed with my network configuration? Am I being MITM’d?

Thanks.



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

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.

Heya,

You can try re-adding the DigitalOcean monitoring repository:

  1. Backup your current /etc/apt/sources.list.d/digitalocean-agent.list file:
  1. sudo cp /etc/apt/sources.list.d/digitalocean-agent.list /etc/apt/sources.list.d/digitalocean-agent.list.backup
  1. Remove the old repository file:
  1. sudo rm /etc/apt/sources.list.d/digitalocean-agent.list
  1. Re-add the repository:
  1. echo "deb [signed-by=/usr/share/keyrings/cloud-archive-keyring.gpg] https://repos.insights.digitalocean.com/apt/do-agent main main" | sudo tee /etc/apt/sources.list.d/digitalocean-agent.list
  1. Update the package lists:
  1. sudo apt-get update

If you still experience issues, it’s recommended to open a support ticket with DigitalOcean. They can help you investigate further and check if there’s any network-related issue with your droplet.

Hope that this helps!

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.