DavidBerdik
commented
9 months ago Hello Justin,
Unfortunately, the formatting of your post seems to be a bit messed up and I am therefore having a hard time understanding what exactly your issue is. That said, I think you may have an issue with how your SSL certificate is configured. When I open https://isseutestgithub.youtube-music-alexa-test.de:4000/dl/ymNFyxvIdaM?f=bestaudio in Chrome, the audio downloads, but clicking on the info icon on the address bar shows the following pop-up.
Additionally, curl also reports an SSL certificate issue:
david@David-PC:~$ curl -v https://isseutestgithub.youtube-music-alexa-test.de:4000/dl/ymNFyxvIdaM?f=bestaudio
* Trying 84.171.124.221:4000...
* Connected to isseutestgithub.youtube-music-alexa-test.de (84.171.124.221) port 4000 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS header, Unknown (21):
* TLSv1.3 (OUT), TLS alert, unknown CA (560):
* SSL certificate problem: unable to get local issuer certificate
* Closing connection 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
justinh998
Hello, I hope someone can help me here. I'm currently quite desperate as I've been dealing with this problem for about 4 weeks. I have this server (youtube-stream-repeater) running in Docker, and it seems to be working fine. For example, when I access https://isseutestgithub.youtube-music-alexa-test.de:4000/dl/ymNFyxvIdaM?f=bestaudio, I get a downloadable file that can be played. However, AWS keeps giving me this error all the time: {'message': 'Device playback error', 'type': 'MEDIA_ERROR_UNKNOWN'}. Is it possible that AWS/Alexa cannot handle the fact that it's not receiving a direct stream (like in pytube for example an pytube link : pytube link ? If there are issues with this, have there been numerous issues reported here, or are people modifying their code accordingly? Here is my code that I changed; everything else corresponds to the current version from wes1993.
I always pass a fixed title:
return stream_ext, "freestyler"Since when I try to execute the code:I always encounter an error:
No other thing has an issue with my website, only Python. I believe this is a general Python problem, and I maybe will come up with a solution for it. Pytube, as used by @DavidBerdik , is rather unreliable. Here is the entire log from AWS of a failed attempt:
I hope somebody can help me