[Flixhq] No stream links are returned for vidcloud and upcloud about api.consumet.org

[riimuru]

@pitsi fixed 👍. they changed the key size from 16 to 32 chars, so I just had to use a different regex.

[pitsi]

Thank you very very much! :)

[hackedXD]

@riimuru This issue seems to have popped up again.

I tried the process done above and it seems to be replicating the same response as before.

The output of both of the following commands

• curl -s "https://api.consumet.org/movies/flixhq/watch?episodeId=19694&mediaId=movie/watch-deadpool-19694&server=vidcloud"
• curl -s "https://api.consumet.org/movies/flixhq/watch?episodeId=19694&mediaId=movie/watch-deadpool-19694&server=upcloud"

Produce the same output of
{"message":"Media Not found."}

[pitsi]

It's almost 7am here and I have just woken up, but I had to check it.

So, on my first try with just curl, the api returned stream links and I was about to say that it was working ok and I would commend later on, with some grep etc to keep the important parts.
Then I tried my script, but it did not work, so I tried curl again. And this time curl returned the "media nor found" message.
I will investigate it more later on, just in case the api has some downtime.

I also noticed that it no longer returns the same urls for vidcloud and upcloud, like it did 2 days ago.

---edit
2 hours have passed since then and I checked it again just now. It does return results like it used to and the script is also working...