Project

General

Profile

Bug #4725

Repo Certificate Problems on Ubuntu Trusty

Added by Ma rc about 7 years ago. Updated almost 7 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Target version:
-
Start date:
2017-11-15
Due date:
% Done:

0%

Estimated time:
Found in version:
release-4.2
Affected Versions:

Description

Im using the bintray repo to install tvheadend on Ubuntu 14.04 Trusty. When I update my repos using apt-get I get the following error:

Err https://dl.bintray.com trusty/release-4.2 amd64 Packages
  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Err https://dl.bintray.com trusty/release-4.2 i386 Packages
  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Ign https://dl.bintray.com trusty/release-4.2 Translation-en_US
Ign https://dl.bintray.com trusty/release-4.2 Translation-en
100% [Working]W: Failed to fetch https://dl.bintray.com/tvheadend/deb/dists/trusty/release-4.2/binary-amd64/Packages: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
W: Failed to fetch https://dl.bintray.com/tvheadend/deb/dists/trusty/release-4.2/binary-i386/Packages: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
E: Some index files failed to download. They have been ignored, or old ones used instead.

Im using the following repo:

deb https://dl.bintray.com/tvheadend/deb trusty release-4.2

History

#1

Updated by Mark Clarkstone about 7 years ago

  • Status changed from New to Accepted

Ma rc wrote:

.. snip ..

There's something weird going on at Bintray atm. I can't even login to check things using my git account. I've opened a ticket with them.

#2

Updated by Mark Clarkstone almost 7 years ago

Ma rc are you still having this issue or has it resolved itself? :)

#3

Updated by Ma rc almost 7 years ago

Yes, it automagically fixed itself :D

#4

Updated by Mark Clarkstone almost 7 years ago

  • Status changed from Accepted to Invalid

Ma rc wrote:

Yes, it automagically fixed itself :D

Thanks for the update - closing :)

Also available in: Atom PDF