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.

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

Can't connect to trackers using HTTP-proxy #9696

Closed
helperman opened this issue Sep 29, 2020 · 2 comments
Closed

Can't connect to trackers using HTTP-proxy #9696

helperman opened this issue Sep 29, 2020 · 2 comments

Comments

@helperman
Copy link

@helperman helperman commented Sep 29, 2020 •
edited
Loading

Please use the search bar at the top of the page and make sure you are not creating an already submitted issue.
Check closed issues as well, because your issue may have already been fixed.

Please read our Contributing Guidelines before submitting your issue to ensure a prompt response to your bug.

Environment

OS: Window 8

.Net Runtime: .Net-Framework

.Net Version:

Jackett Version: v0.16.1431

Last Working Jackett Version: all versions have this issue

Are you using a proxy or VPN? yes

Description

  1. Use proxy URL: https://antizapret.prostovpn.org/proxy.pac
  2. Press "Test" button to test connection to https://1337x.to

An error occurs as well as for many other trackers.
This site https://1337x.to works in my browser with the "proxy.pac" setting but doesn't work in Jackett.

Logged Error Messages

log.txt

Screenshots

Here is my options.
I chose only HTTP-proxy and set its url: https://antizapret.prostovpn.org/proxy.pac
00000572

Test button with error:
00000571
@helperman helperman changed the title [1337x] Exception (1337x): Удаленный хост принудительно разорвал существующее подключение.: The SSL connection could not be established, see inner exception. (Test) Can't connect to trackers using HTTP-proxy Sep 29, 2020
@garfield69
Copy link
Collaborator

@garfield69 garfield69 commented Sep 29, 2020

your error message (once translated by google) reads Remote host forcibly terminated existing connection
this implies that you are being blocked from accessing 1337x.to.

Your log shows that in response to Jackett trying https://1337x.to/cat/Movies/time/desc/1/ the 1337x server is returning

<html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx/1.14.2</center>
</body>
</html>

something about the proxy you are using is not compatible with 1337x web site.
@ngosang @ilike2burnthing have you anything to add regarding this user's issue?

Loading

@ilike2burnthing
Copy link
Collaborator

@ilike2burnthing ilike2burnthing commented Sep 29, 2020 •
edited
Loading

Jackett can't process the script (to my knowledge it has no way of doing so). You would have to use the actual proxy URL, however:

    // WARNING! WARNING! WARNING!
    // You should NOT use these proxy servers outside of PAC file!
    // DO NOT enter it manually in any program!
    // By doing this, you harm the service!
    return "HTTPS proxy-ssl.antizapret.prostovpn.org:3143; PROXY proxy-nossl.antizapret.prostovpn.org:29976; DIRECT";

What you do with that warning is up to you.

EDIT: given that the script is regularly updated, chances are that the port is changed as well, so it would be a pain to use. I'd suggest looking for a different proxy.

Loading

@ilike2burnthing ilike2burnthing mentioned this issue May 9, 2021
Open
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
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@garfield69 @helperman @ilike2burnthing