Can't connect to some PeerTube instances

[jeberger]

NewPipe version 0.19.4 refuses to connect to some PeerTube instances. For instance, when I go to Settings → Contents → PeerTube instances, click on the + button and type "https://video.ploud.fr/", I get a message: "Cannot validate the instance" and the instance is not added to the list.

Other PeerTube instances work (eg. https://hostyour.tv)

[B0pol]

I can't reproduce

[gkeegan]

Is it possible these instances are being blocked by either your network or an adblock list on your phone?

[Stypox]

I can't reproduce either, though maybe this has something to do with certificates. For example, on my phone the default instance (i.e. framatube) gives the same error because of a missing certificate on my phone

[jeberger]

The same URL works in Firefox on the same phone and network, so this should rule out a network or adblock issue. Is there a way to check or get more info to see if it is a certificate issue?

[Stypox]

For me it works well in browser, too. Maybe it has something to do with the availability of TLS protocols? Maybe some are disabled in NewPipe? @mqus

[mqus]

Yeah it could be that the page only supports TLS 1.3 or only TLS ciphersuites which are not supported by the android version.

@jeberger what is your android version?

[jeberger]

@jeberger what is your android version?

It's the stock KitKat ROM on a Samsung Galaxy Note 3. Just tried with the stock browser and it can't connect either: it returns an SSL error.

[wb9688]

Then it's not our issue. Upgrade to a newer Android version.

^{It might be able to patch that in through Google Play though, but we don't want to depend on proprietary crap.}

[mqus]

Upgrade to a newer Android version.

That is not possible in many cases, so you could also send a nice email to the instance admin where you ask for enabling the right ciphers and at least tls 1.2.

EDIT:

the right ciphers

quoting my own post in #2792, at least one of the following ciphers should be enabled, from most preferred to least preferred (but still safe):

• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
• TLS_RSA_WITH_AES_256_CBC_SHA
• TLS_RSA_WITH_AES_128_CBC_SHA

[ale5000-git]

microG is also able to patch it with ProviderInstallerImpl.

[Younes-L]

I'm having the same problem on Android pie, newpipe 0.20.5 .
I can add peertube.pontostroy.gq (follows 623 instances) to newpipe but not tube.4aem.com (follows 1049 instances)

Let me know if I should create a new issue

[mqus]

Please create a new issue with the exact error and how it occurred. This issue should not exist on android pie (9?), since it includes modern crypto.

[Younes-L]

@mqus done #5115