-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
get-latest-release url not working due to invalid certificate #33014
Comments
Hi @dirkf, thanks for the reply. I have looked at the referenced articles. However, I have come to the conclusion that the referenced articles do not offer a solution to the problem I have mentioned, and probably do not relate to it. Perhaps my description was not sufficiently clear. I am not talking about a bug in the software. I am also not talking about how youtube-dl makes its updates. I'm talking about the fact that the guide on the website describes a workflow that doesn't work. I'm talking about the manual download path that is described there. A fix in a software that you never get does not solve the problem of getting it. Now for the alleged reason: karstengit's reply ("#32495 (comment)") states that a service provider called rh-tec Business GmbH is blocking access for requests from Hamburg. However, this cannot be the reason for the error occurring here and it also makes things more complicated than they actually are. It is true that I myself am also based in Hamburg and theoretically the responses reporting an error could be manipulated by an intermediary service provider (if its his certificate that's delivered). However, the error also occurs on three servers that are located in different federal states within Germany. Access to the server to which “yt-dl.org” refers is possible. However, the SSL certificate returned is that of the network provider. The response, which is encrypted with the key belonging to the certificate, is also that of the correct server - because with wget, which ignores the certificate, the download works and I get the correct binary. So I'm not reporting that the problem is occurring. Rather, I am reporting that the website is steering users into the problem without offering a solution. Placing possible reasons for an error as an exclusion in the specifications for new issues is certainly not an ideal position for the first occurrence of this information. The simplest solution would be to point out in the update guide of the website that an incorrect certificate is currently being used, stating the certificate information. The other and better solution would be to fix the configuration of the web server so that either the correct certificate is used or - if this is not possible for whatever reason - to additionally listen to the web server at the address (“aries.uberspace.de”) that is pointing to the same ip and to reference the same download link with these domain in the update guide. |
The main guidance will be updated when #31585 is resolved. Meanwhile, what you should have learned from reading #30839 is that (a) that guidance is obsolete (b) a good (for some definition of "good") version of the program is available from the GH nightly release site. If you don't like that, maybe yt-dlp is what you need. |
Hi there, i have deleted the template related to youtube-dl issue requests since this is actually a report related to the webpage providing the release. I wasn't sure where would be the best place to put the issue.
The website ("https://ytdl-org.github.io/youtube-dl/download.html") is referencing the url "https://yt-dl.org/downloads/latest/youtube-dl" to get the latest release version. The site isn't reachable with curl due to a certificate identifying as part of uberspace.de that seems to be the provider of the server the website is hosted on.
Happy new year🎆
The text was updated successfully, but these errors were encountered: