DoodStream is now IP-locked and should be used via MFP #604
Labels
No labels
MediaFlow Proxy
autorelease: pending
autorelease: tagged
bug
documentation
duplicate
enhancement
help wanted
invalid
question
wontfix
🇩🇪 German
🇫🇷 French
🇮🇳 Indian
🇸🇦 Arabic
🌐 Multi
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Creepso/webstreamr-github#604
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Maybe a proxy issue?
Just reporting because it has around two days like this.
you got it exactly right, the non-warp proxy was in a range that doodstream didn't like. I restarted it, it got another IP and now it seems to be fine. thx!
let's keep this open, I want to add such a check and also one for hubcloud to the healthcheck if possible to find this earlier. and then we can have some kind of status page which shows this
is doodstream still working even? I saw a "wrong IP" response via cURL test request. if they're IP-locked now, we can tunnel it via MFP
No dood work ok for me. They are not ip locked.
its still not working on your public instance
*again not working :)
Working again? Didn't change a thing btw and maybe that's good 😆
yes working now
Dont work now...You should gind a proper solution for this I guess
From my experience they "IP-Lock" the stream when the stream is flagged, but not as flagged as the ones that lead to no stream at all.
Very weird ik
Than why same links work on private instance?
That means they might flag the IP and not the stream because in this case the dood is failing on all links not only on particular strems...
This scenario happens for example on Vidmoly, where they flag the IP and they give you a captcha to solve before playing the video. In the mean time changing the IP work just fine. On vidmoly this can be prevented(by waiting between requests) because on my tests they flag the IP if you do 3 fast requests.
Well they work on private instance cause it has a different IP. That said I might be wrong
we could wrap doodstream with MFP and offload the responsibility of making it work to users basically :) that should deal with ip locking too. but needs potentially more setup and effort because of MFP. it should also make doodstream work on android stremio I think
Yes it would be better like that...
Also, there is doodstream support on mediaflow or that is not working? Needs change?
I think just a small fix needed on the actual doodstream code on mediaflow...The problematic part should be ranges...It works on play but it stops when you seek...
But if mediaflow fixes the stream to play on android than is a must.
Anyway you can try it but I am using another extractor called Vidoza(ip locked) through mediaflow and does the same as dood using it through mediaflow...brakes on seek...I dont know if this is a range header issue and if the reason is stremio or mediaflow...
Same code work very good on version 1.5.7 on android lol for both of them.
So i dont think wraping it through mediaflow will fix it on android(at least for the versions from 1.6.2 and later...
@GLlgGL if you're motivated you can PR a fix/update for the doodstream extractor to MFP 😁
in the mean time I disabled the doodstream extractor on the public instance already a while ago
From the last time I checked dood will break on seek using mediaflow...
Firstly changes should be made on the extractor as its not working as it is now...
Maybe next week I can try when I will be at the office as working from home is impossible with my kids lol.
Good news.
I made dood work through mediaflow...working well also on android(also on its latest version).
https://github.com/mhdzumair/mediaflow-proxy/pull/206
Will do a PR here as soon as he merges my PR there
Why not close this? :D
Also push an update to the public instance I want to test this on public instance
Forgot about it. Fixed in
a00fa2c3d6Deployment happens ~ 1 hour after tagging. Everything is deployed.
Making doodstream work requires a residential IP or special proxy though
You are talking for MFP?
Whatever makes the requests. In this case now mfp, yes. But you'll notice with 4xx errors otherwise anyway
I deployed MFP at home on a raspberypi so no problems for me...And I like to use my ip and not proxy because no problem at all at my country about watching things online...
I ofcourse do have some obfuscation like Pihole, Unbound and dnscrypt-proxy with relays :)
Still no new version. 2 hour after
Ah sorry, I misunderstood. Yeah , it should have been released yesterday already. I'll report it to elfhosted
Still nothing new yet
Why you dont deploy it on vercel? Or cloudflare or render?
Or they do have limits?