Closed eur0pa closed 2 years ago
Sometimes the sponsorblock servers goes down. This could be the reason for the error. You can check the status of their servers at https://status.sponsor.ajay.app/
@arebokert nope, curl works fine
~
❯ curl -s 'https://sponsor.ajay.app/api/skipSegments?videoID=o2ixj0m4F_E'|jq
[
{
"category": "sponsor",
"actionType": "skip",
"segment": [
0,
2.939796
],
"UUID": "0f8f9dd3d6e4357ff07833b5c410976022d2fb53e778d0915a612ed18058373e",
...
Thanks for the report, I am seeing it too.
Running curl
in the same container (on the sponsorblock api) works :thinking: So far I have no clue about the issue.
I am trying to bump to Crystal to 1.2.2 but I got this issue.
I think the cause was an outdated certificates store in the docker image crystal-alpine 1.0.0. I bumped to 1.1.1 and it seems to works now.
Tell me if that's not the case :)
Seems to be working fine using the new Docker image
Latest docker, worked fine last night