I'm trying to update my DigitalOcean VPS that has my CouchDB running on it and I get this error message:

        sudo apt-get update

   Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
   [109 kB]
   Hit:2 http://mirrors.digitalocean.com/ubuntu xenial InRelease
   Hit:3 http://mirrors.digitalocean.com/ubuntu xenial-updates InRelease
   Hit:4 http://mirrors.digitalocean.com/ubuntu xenial-backports InRelease
   Hit:5 http://ppa.launchpad.net/certbot/certbot/ubuntu xenial InRelease
   Hit:6 http://ppa.launchpad.net/ondrej/apache2/ubuntu xenial InRelease
   Ign:7 https://apache.bintray.com/couchdb-deb xenial InRelease
   Ign:8 https://apache.bintray.com/couchdb-deb bionic InRelease
   Ign:9 https://apache.bintray.com/couchdb-deb xenial Release
   Ign:10 https://apache.bintray.com/couchdb-deb bionic Release

   ...

   Err:19 https://apache.bintray.com/couchdb-deb xenial/main amd64 Packages
      403  Forbidden
   Err:20 https://apache.bintray.com/couchdb-deb bionic/main amd64 Packages
      403  Forbidden
   Fetched 109 kB in 4s (22.6 kB/s)
   Reading package lists... Done
   W: The repository 'https://apache.bintray.com/couchdb-deb xenial
   Release' does not have a Release file.
   N: Data from such a repository can't be authenticated and is
   therefore potentially dangerous to use.
   N: See apt-secure(8) manpage for repository creation and user
   configuration details.
   W: The repository 'https://apache.bintray.com/couchdb-deb bionic
   Release' does not have a Release file.
   N: Data from such a repository can't be authenticated and is
   therefore potentially dangerous to use.
   N: See apt-secure(8) manpage for repository creation and user
   configuration details.
   E: Failed to fetch
   
https://apache.bintray.com/couchdb-deb/dists/xenial/main/binary-amd64/Packages
   403  Forbidden
   E: Failed to fetch
   
https://apache.bintray.com/couchdb-deb/dists/bionic/main/binary-amd64/Packages
   403  Forbidden
   E: Some index files failed to download. They have been ignored, or
   old ones used instead.

I've never had an issue doing this before. Any ideas on where to go from here?


--

Kindest Regards,

Bill Stephenson
Tech Support
www.ezInvoice.com
1-417-546-8390

Reply via email to