Skip to content
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.

Sign up for GitHub

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

Jump to bottom

YggTorrent updates #434

Open
Gregsr opened this issue Jun 14, 2024 · 19 comments
Open

YggTorrent updates #434

Gregsr opened this issue Jun 14, 2024 · 19 comments

Comments

@Gregsr
Copy link

Gregsr commented Jun 14, 2024

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
@antonsoroko
Copy link
Contributor

antonsoroko commented Jun 21, 2024 •
edited
Loading

@Gregsr
this probably will be fixed by #434
although, i can't really test it because of cloudflare anti-bot protection.

if you do not get cloudflare anti-bot protection then you can make local changes from PR to see if they work.

@Gregsr
Copy link
Author

Gregsr commented Jun 21, 2024

@Gregsr this probably will be fixed by #434 although, i can't really test it because of cloudflare anti-bot protection.

if you do not get cloudflare anti-bot protection then you can make local changes from PR to see if they work.

I made the changes and I have this error (my credentials are ok):
T:13232 critical : [script.elementum.burst] [yggtorrent] Login failed: 403

@antonsoroko
Copy link
Contributor

@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

critical <general>: [script.elementum.burst] [yggtorrent] Login failed: 403
debug <general>: [script.elementum.burst] [yggtorrent] Failed login content: '<!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title>...more HTML page content...

which is cloud flare anti-bot page.

@Gregsr
Copy link
Author

Gregsr commented Jun 22, 2024

@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?

@antonsoroko
Copy link
Contributor

antonsoroko commented Jun 22, 2024 •
edited
Loading

@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.

I notice that the search is still being conducted before logging in.

where you see it? i guess in UI - this just means that search process was started.
see the log starting from line 3913 - burst does login, fails, stops - search was not conducted.

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).
thus in kodi UI you anyway will see that search is started - maybe that confused you.
so it is logical. otherwise it would be super hard to do all checks (if you have login/pass set, if those login works, if site wotks, etc) in advance and only then show you that search was started.

@Gregsr
Copy link
Author

Gregsr commented Jun 23, 2024

@antonsoroko thanks for the explanations and solutions. I will try it on Windows 10 and Google TV.

@antonsoroko
Copy link
Contributor

antonsoroko commented Jun 27, 2024 •
edited
Loading

@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
note that you need to catch "cloudflare anti-bot page" first, and then you can push cookies.

then you can start elementum and check if .kodi/temp/burst/common_cookies.jar was updated with cf_clearance cookie for ygg domain.

if not then it might be a bug of that chrome extension (nothing we can do), but you can add this cf_clearance cookie manually (you can take it from dev panel in your browser).

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.

@Gregsr
Copy link
Author

Gregsr commented Jul 4, 2024

@antonsoroko I tested with SyncMyCookie. It seems that login is ok (I'm not a specialist) but I receive 0 result.
Here is the log file https://pastecode.io/s/j0rf2hho

@antonsoroko
Copy link
Contributor

@Gregsr can you please enable "Log debug messages for parsing" in burst advanced settings, and create log again. Then disable that setting.

@Gregsr
Copy link
Author

Gregsr commented Jul 5, 2024

@antonsoroko here is https://pastecode.io/s/dt7rgt2s

@antonsoroko
Copy link
Contributor

@Gregsr right now you have some other error

<general>: [script.elementum.burst] b'https://www.ygg.re/auth/process_login' failed with ConnectionError(ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))):

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".

@Gregsr
Copy link
Author

Gregsr commented Jul 5, 2024

@antonsoroko the parameter "login_path": "/auth/process_login" in providers.json seems to be not the good adress (via Chrome, it is a blank page). I have changed it by "login_path": "/auth/login" (via Chrome, I get to the login page) and I have got this message in the log file but 0 result.
<general>: [script.elementum.burst] [yggtorrent] Login successful

Here is the log file https://pastecode.io/s/hnm97j77

@antonsoroko
Copy link
Contributor

antonsoroko commented Jul 5, 2024 •
edited
Loading

@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.

@Gregsr
Copy link
Author

Gregsr commented Jul 5, 2024

@antonsoroko here is https://pastecode.io/s/0sz2jkg4
Thanks for your help

@antonsoroko
Copy link
Contributor

@Gregsr hm, I still see html content of login page instead of results page.
Have you pushed cookies in chrome extension after login? Maybe they expired, please push cookies again.

Also try without cookie sync (delete cookie for ygg in chrome extension).

@Gregsr
Copy link
Author

Gregsr commented Jul 5, 2024

@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)

@elgatito
Copy link
Owner

elgatito commented Jul 6, 2024

Set useragent setting in Burst to be the same as the browser that uses cookie sync.

@antonsoroko
Copy link
Contributor

antonsoroko commented Jul 6, 2024 •
edited
Loading

@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 ygg_ cookie name for login cookie), when you will have problem with cloudflare again - try to do cookie sync again.

Also set user agent, like me and elgatito said above.

@elgatito
Copy link
Owner

@Gregsr @antonsoroko is there anything to fix/change? Or we can close this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@elgatito @Gregsr @antonsoroko