-
Notifications
You must be signed in to change notification settings - Fork 10k
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
[DPlay] unable to download free or premium episodes from dplay.no, es.dplay.com and it.dplay.com with user account #24554
Comments
I've also tried with this URL format: |
The problem seems to be with reCAPTCHA. dplay.no has implemented it on the login page. If I use the --cookie attribute with cookies catched with this Chrome extension it works |
Same problem with es.dplay.com and it.dplay.com, maybe you can edit title to add this urls too so can be fixed all of them at the same time. |
OK, done. But I doubt this could be fixed that easily. reCAPTCHA is hard to script around. Better just use my --cookie approach |
I'm trying the cookie approach but i cant login , which cookie is the one needed? there are a few of them.
Bests. |
I just used every cookie that those extensions made. If you use the Chrome extension click on:
|
what is your exact command you also use --username --password appart from --cookie ? |
No, I didn't use --username or --password. This is my exact command line: |
Maybe is different dplay.no from es.dplay.com and it.dplay.com it keeps asking me the username and password. |
I think you marked all the duplicates as duplicate and nwo there is no original bug one reporting the bug, isn't it? I dont see any opened bug with this bug but 5 of them closed as duplicate. |
I think the same problem is tracked in open issue #22972 |
that bug is from 2019, differenet output error, the patform changed 3 times since 2019. |
What difference do you see? The errors seem to me to be the same. |
|
Definitely agree with this, and definitely the reason the older bug appeared must have been different, but I still don't see the difference in the error output, outside of probably being ran on different systems (Windows vs something else). The stack traces seem to touch on the same code paths, giving the same error messages? Definitely trying to fix the older issue would make the developer hit this issue either way, so I think fixing the other bug would also fix this issue. Hopefully a developer pitches in with any info. |
This particular bug is probably very difficult to fix without adding a GUI element that could be used to solving the captcha on the login page. That's also how this differs from #22972 in that Dplay didn't use captcha back then. Also the problem I had was easily bypassed with a browser cookie capture, while a cookie file didn't fix the problems in #22972. |
I guess I'll try to get a cookie from Chrome then, because using a cookie from the equivalent Firefox extension changed nothing for me, giving me the same error. I would also still like someone to point out if they actually see any difference in the errors between the issues, as everyone just keeps mentioning what the pages themselves have changed since the first issue was opened. They still seem the same to me. |
me too wit firefox cookie is not working but i did not try with chrome cookie, did it work? |
Hi have you tried ? with chrome cookie, no luck |
Finally had time to try it, and the chrome cookie worked for me. |
Hi, please i report my issue here but i use dplay.it, ahve you used the same website? If yes, can you help me ? I have tried a lot of extension to export cookie from chrome, but anyway doesn't works, seems a youtube-dl trouble. |
Checklist
Verbose log
Description
I'm unable to download free or premium content from dplay.no with a user account. I've been able to download free content earlier, but now a (free) user account is required. I've made a test account with a disposable e-mail address, and used this commandline to test the download:
But I get this errormessage:
(I've verified that the account works in a browser)
The text was updated successfully, but these errors were encountered: