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
Fmovies not working #428
Comments
Semi-offtopic. Because arch is on npm 8.x, I also gave alpine a try that is on npm 9.x. Both fmovies and flixhq fail with ipv6 enabled. Fmovies shows the same as above, while flixhq shows this timeout error
If anyone else does notice this with ipv6 enabled, please share your experience. |
Was fmovies fixed or changed since then? I just noticed that there were new commits in the repo after ~2 months of silence, so I gave it a try and it now returns this error about a maximum number of retries. It also take like 30+ seconds to reply.
Sadly, I no longer have the local instance so as to test, I deleted it in late May. |
Here is the self-hosted url, if you guys wanna try something https://conmet.vercel.app I have encountered similar issue with flixhq endpoint, and I opened a issue at consumet.ts repo, since the REST API is just a wrapper for it. issue |
Thank you for letting me try your instance. However, it returns the same error as the one I describe at the start
If I am doing something wrong, please tell me. |
Something was fixed with the last commit, the one from 2 days ago, and the api now returns something more meaningful.
Let's hope it will really return results one day :) |
And today's commit increased the response time from just milliseconds to ~30 seconds or more, even 1+ minute! The fastest I have seen is ~25 seconds and the slowest is this ~1.5 minute delay!
---edit
---re-edit, 12 hours later
|
New week, new error :p
On top of that, tmdb is now broken as well, with a 401 error for search and info. The watch function still works though.
|
And the watch function for tmdb is now broken too :(
|
@forsyth47 |
Today, 1 year after opening the issue, I had the chance of making a new vm to test if anything has changed. And sadly nothing has changed, fmovies remains broken, and it even has the same errors like last year :( Libgen is also broken. |
Not sure if this would fix the original issue but Fmovies changed their domain at some point from fmovies.to to fmoviesz.to I've never setup consumet locally myself but I wonder if changing this line would fix some problems (in the consumet.ts repo): |
Describe the bug
As mentioned in the title, the fmovies provider does not work, neither at your instance, nor at the one I host locally
Steps to reproduce
Use the api's function to search something through fmovies. Using your instance that returns a 403 error
Using my instance, hosted locally
The top error is with ip6 disabled (kernel parameter ipv6.disable=1), the bottom one is with ipv6 enabled.
Expected behavior
I don't know how the results from fmovies actually look like, but I assume they should look like the ones from flixhq
Actual behavior
See above. The reason I tried with ipv6 support disabled is explained below.
Additional context
Flixhq returns this error and fails with anything when ipv6 is enabled. That is why I tried both providers with it being disabled.
The text was updated successfully, but these errors were encountered: