Closed anonymousje closed 1 month ago
I have the same issue, tried a bunch of languages and comes back with "No subtitles found"
Screenshot
Debug ``
~ ➜ mov -x inception
``
Desktop:
Same exact issue on Linux Mint.
I have the same issue too!
Same on Ubuntu and android
same issue on arch
Same issue on... (nevermind).
The real issue is not the subtitles or anything similar like their language. The main url lobster uses in order to decrypt what is needed now leads to a 404. In turn, the json_data variable contains gibberish instead of links for video and subtitles which are passed to the player that will play them. Unfortunately, the script does not have an info line that would say "no video", like it has for the lack of subtitles, so the user is only about the lack of subtitles and nothing more.
So, until justchockingaround fixes the used domain or creates a new one, nothing can be done.
For now there seems to be a workaround posted on discord I would recommend a (distrobox,toolbox) container for this if possible for testing, i myself had it tested on a VM inside EndeavourOS.
Too bad I am not on discord then :(
https://lobster-decryption.netlify.app/ Site is down because @justchokingaround did not pay the bill for netlify. Use this repository https://github.com/justchokingaround/lobster-netlify-api as a backend service.
Ahhh selfhosting :D
That is what I tried yesterday. I installed nodejs/npm, cloned the repo, run npm install to install any dependencies, then npm start and it failed. What did I do wrong? Alpine edge guest, running on virtualbox, on debian unstable host, both x64.
Ahhh selfhosting :D
That is what I tried yesterday. I installed nodejs/npm, cloned the repo, run npm install to install any dependencies, then npm start and it failed. What did I do wrong? Alpine edge guest, running on virtualbox, on debian unstable host, both x64.
You still need netlify, typescript, and do a configuration in your lobster config, and inside the repo you cloned, do npm i
and then netlify dev
, if it tries to find a browser described(yes i had this issue too even though it was uninstalled, it was looking for cachy-browser), either configure netlify or just install that specific browser its looking for xp..
I have no netlify binary after installing it with npm. I guess it is because I did not allow it to install globally. Nevermind, I will wait for the dev to fix the site.
If someone has his own domain, please consider hosting the decrypter thing.
you don't need to install the netlify binary globally, i did read the message on discord and then tried setting it up. At first i thought maybe i could modify it to run as a nodejs server but then gave up (idk nodejs), and then just used netlify cli.
EDIT: I'm on Fedora 40
You do need nodejs and npm installed (which btw might already be installed if you're on fedora)
npm i
or npm install
lobster --edit
and add the following in the config:
json_from_id() {
json_data=$(curl -s "http://localhost:8888/.netlify/functions/decrypt?id=${source_id}")
}
by default netlify server would run on 8888 but if it doesn't change it to whatever port it runs on
touch /home/YOUR_HOST_NAME/.config/lobster/lobster_config.sh
(change the YOUR_HOST_NAME to your username and then add it to the config.netlify dev
(if you didn't installed netlify globally you can execute it using npx netlify dev
as running npm i
should've installed it as a dependency under the project, but you should be in the project directory).don't close the terminal or the server will stop... and you'd need to start the server using netlify dev
(or npx netlify dev
in the project directory) each time you wanna use lobster, unless you run it all the time or set it to start at boot ig.
If you don't want to run a local server you can host it on netlify, then in the config you'd add something like https://your-sub-domain.netlify.app/.netlify/functions/decrypt?id=${source_id}
tho i haven't tested that myself. Also you'd have to configure build settings while deploying.
Btw when you run the server using netlify dev
or npx netlify dev
it would show 404 after opening it up on default browser and it would shift to the static version as you don't have all the things needed but it still works fine
Thank you for the very detailed explanation.
Out of all the things you describe above, the only think I would not even think to do is the npx one on step 4. So, I managed to make the server run, I saw the text on your first screenshot as it scrolled up and it ended up with this
› Error: There was a problem setting up the Edge Functions environment. To try a manual installation, visit https://ntl.fyi/install-deno.
(node:2838) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
I ignored it, opened a browser on http://alpine.local:8888
and saw the 404 message you mention. But when trying curl on it with an id (the ones mentioned below are valid and are for deadpool), I got an "internal server error" on the client side
$ curl http://alpine.local:8888/.netlify/functions/decrypt?id=1612803
{"error":"Internal server error"}
$ curl http://alpine.local:8888/.netlify/functions/decrypt?id=19694
{"error":"Internal server error"}
and these on the server side (the open terminal that runs npx netlify dev
)
Request from ::ffff:192.168.1.2: GET /.netlify/functions/decrypt?id=1612803
TypeError: Cannot read properties of null (reading '0')
at getMeta (/root/lobster-netlify-api/netlify/functions/rabbit.ts:720:31)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at newReq (/root/lobster-netlify-api/netlify/functions/rabbit.ts:727:7)
at main (/root/lobster-netlify-api/netlify/functions/rabbit.ts:778:10)
at Object.handler (/root/lobster-netlify-api/netlify/functions/decrypt.ts:16:20)
Response with status 500 in 682 ms.
Request from ::ffff:192.168.1.2: GET /.netlify/functions/decrypt?id=19694
TypeError: Cannot read properties of null (reading '0')
at getMeta (/root/lobster-netlify-api/netlify/functions/rabbit.ts:720:31)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at newReq (/root/lobster-netlify-api/netlify/functions/rabbit.ts:727:7)
at main (/root/lobster-netlify-api/netlify/functions/rabbit.ts:778:10)
at Object.handler (/root/lobster-netlify-api/netlify/functions/decrypt.ts:16:20)
Response with status 500 in 230 ms.
It goes without saying that 192.168.1.2 is my pc's ip and that I use avahi (mdns) on every system on network, so instead of the ip of the alpine vm, I use alpine.local, because
$ avahi-resolve -n alpine.local
alpine.local 192.168.1.104
@pitsi
directly scrapping thorugh curl did gave 500, however when using lobster it somehow worked though there still are some errors Invalid input string format: window.ReactNativeWebView
Now here's what i think, FlixHQ probably changed some things (cuz its using different ids when using lobster), but that doesn't answer why the api can't be deployed on netlify (i've tried to deploy it but rabbit.ts causes the build to fail) or maybe netlify changed some things or maybe i'm doing it the wrong way idk...
You are right about running curl alone, it returns no results. Thank you for enlightening me! :) One minor annoyance I found. On line 379 that holds the url for the json_data variable, the https part had to be changed to http for the whole thing to work.
the plan is to switch from netlify to https://www.koyeb.com/ (afaik it has unlimited requests for free unlike netlify), I just haven't had time yet to do so, as I'm very busy (physically) atm. if anyone can help with the setup of the API it would be very helpful. otherwise u can just wait for me to do it.
ty @pitsi for the original explanation and thanks a lot @FurqanHun for the elaborate explanation of how to self host the decryption API server, that helps people out a lot and I haven't done it yet <3
@justchokingaround still having this issue on arch linux, lobster version 4.3.3.
It is because the new site that lobster uses now leads to a 404. Curl parses its entire page as an html, so the contents of the json_data variable are gibberish again and in turn the script fails to run. Basically whatever I explained last time.
@judexgauss @pitsi this is a known issue, and even if the api was working the site would still show 404 cuz there's no frontend… anways the reason is the new site of migration randomly banned the dev :( (maybe alts too idk), the only solution for now is to self host, either locally or on a service like netlify…
Describe the bug Try to search for a show, select the episode and error "No subtitles found" occurs.
To Reproduce Steps to reproduce the behavior:
Expected behavior VLC or MPV should open to play the video
Desktop (please complete the following information):