-
Notifications
You must be signed in to change notification settings - Fork 117
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
YggTorrent updates #434
Comments
I made the changes and I have this error (my credentials are ok): |
@Gregsr you need to enable debug log in kodi to see real root cause, see https://elementum.surge.sh/contribute/log/ as guide (you only need kodi part for this issue). in my case i have
which is cloud flare anti-bot page. |
@antonsoroko here is the log file https://pastecode.io/s/5o2by9ak I notice that the search is still being conducted before logging in. Is this logical since it is now necessary to be logged in to see the results? |
@Gregsr see line 3951 - you also get cloudflare page. the solution was to use cookies from browser, see #414 , but in recent versions of chrome that extension to sync cookies stopped working for me (either chrome or github changed something). another solution is to install Jacket server and use https://github.com/fugkco/script.elementum.jackett if you really need ygg - then Jacket probably will work for you, iirc Jacket uses "browser emulation" to bypass cloudflare, but it is a separate application that you should install somewhere and keep it running.
where you see it? i guess in UI - this just means that search process was started. but login is a part of search process and done before search, every time (if you already have cookies - burst use cookies, but burst still does login to see if you have cookies). |
@antonsoroko thanks for the explanations and solutions. I will try it on Windows 10 and Google TV. |
@Gregsr actually SyncMyCookie works with latest google chrome (i use opera and opera has some issue with this extension), so you can try it - read #414 then you can start elementum and check if if not then it might be a bug of that chrome extension (nothing we can do), but you can add this also you need to set custom "User Agent" in burst settings. You also can see its value in dev panel in browser. if it is too complicated (cloudflare is tricky beast) - then try Jacket. |
@antonsoroko I tested with SyncMyCookie. It seems that login is ok (I'm not a specialist) but I receive 0 result. |
@Gregsr can you please enable "Log debug messages for parsing" in burst advanced settings, and create log again. Then disable that setting. |
@Gregsr right now you have some other error
Looks like ygg was unreachable at that moment. (Or your internet provider blocked connection to ygg.) Need a new log file with "Log debug messages for parsing". |
@antonsoroko the parameter Here is the log file https://pastecode.io/s/hnm97j77 |
@Gregsr it is not about page, but about POST request, use dev panel in browser to see how it works and read some explanation about post and get in internet, if you are unfamiliar with web requests. Anyway, as you can see in the log, right now you get login page instead of result page, which means that Login didn't work. You see "Login successful" because you use wrong page and that page does not give "error message", so our check thinks that everything is ok. Please change back login_path and make log with debug parsing, like I requested above. So we can see if you get cloudflare or something else. Unfortunately, ygg always blocks me (probably because I'm not in France), so I can't test it. |
@antonsoroko here is https://pastecode.io/s/0sz2jkg4 |
@Gregsr hm, I still see html content of login page instead of results page. Also try without cookie sync (delete cookie for ygg in chrome extension). |
@antonsoroko I deleted cookies in chrome extension and I have got results... (see log file https://pastecode.io/s/vkdwjtmk) At the moment, I don't have the cloudflare page to push cookies before login (I tried after having deleted all my cookies from Chrome too) |
Set useragent setting in Burst to be the same as the browser that uses cookie sync. |
@Gregsr if you have results then it means that changes that I made works. I am not sure if "cookies sync" still works for ygg correctly (it used to work, and as I can see they still use Also set user agent, like me and elgatito said above. |
@Gregsr @antonsoroko is there anything to fix/change? Or we can close this issue? |
@elgatito it works for me with cookie sync. without - cloudflare page. |
It depends, and I use SyncMyCookie. Indeed, if it has to go through the Cloudflare page, it doesn’t work; otherwise, it works. I have the impression that when it works, my IP was previously recognized via Chrome on Windows by going through the Cloudflare page. At that point, I can use Kodi for a few hours or days. I noticed in the file |
It is the opposite. We sync cookies from the browser to pretend that we were already passing cloudflare protection pages (your browser was doing that). But of course, there are other possible checks. Cloudflare can even detect if you were accessing pages using different OS of the device, also the simplier UserAgent check that would be different with every Chrome update. That is annoying, but probably only the periodic cookies update can help with it. |
It seems to me that it was the same user agent when I tried some time ago, but I will try again and keep you updated. |
I have the same issue for ygg and some other trackers (so I had to manually add cf_clearance cookie into file). And looks like soon chrome will disable it (and many other extensions), since it was not updated to their new standards. I do not know what we can do here. |
YggTorrent adress has changed: https://www.ygg.re/ and the site structure has changed too. The site is now only accessible to members, and I assume the login process is different.
Thanks
The text was updated successfully, but these errors were encountered: