Jackett: [horriblesubs] Exception (horriblesubs): Got redirected to another domain. Try changing the indexer URL to https://horriblesubs.info/.: Parse error (Test)

Created on 2 Jul 2018  Â·  29Comments  Â·  Source: Jackett/Jackett

Jackett version: Latest (0.8.1201.0)
Mono version (if not using Windows): n/a


seems like the fix in #2605 is now causing an issue when they've moved back to forced-https.

recommend the primary and secondary links be swapped so that it is default https again.

Help wanted

Most helpful comment

All 29 comments

Looks like they changed the site too.
https://horriblesubs.info/lib/latest.php?value= is no longer available.
The new latest list only show the series title, not the individual releases.
Is there another list containing the latest releases/search results one by one instead of this grouped view?

If not the indexer needs to be re-implemented as native indexer.

Came here to report this error, glad I checked before posting.

@Lauwens how do I apply it to horriblesubs.yml?

@Lauwens updating the SiteLink to that, still shows an error for me

Tried updating the Site Link to that also and no luck for me.

I'm experiencing this issue as well any progress on a workaround?

The reason the link from @Lauwens won't work is that Jackett continuously applies a final / at the end of any Site URL. However this specific URL does not reach anything with the / added and I can see no way to remove it.

The api.php output is not useful (it's what's used by the main page).
This needs to be rewritten as native C# indexer

Indeed wont work anymore and will need a new indexer, (as stated in their update) they changed it to go to an extra page for monetizing reasons

Finally, yes, it takes an extra click to download something now. I'll be honest. This is done mainly to improve revenue and SEO.

Could you link the source for that?

Not that I don't believe you, I just want to read the whole thing. :-)

Thanks a bunch!

On Wed, 11 Jul 2018, 11:55 Lauwens, notifications@github.com wrote:

It is on the main site:
https://horriblesubs.info/2018/07/j-list-ax-giveaway-and-site-updates/

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Jackett/Jackett/issues/3318#issuecomment-404128991,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APSf5NIYRiA6b5JtFm-0U51jyzb-4dTCks5uFdmggaJpZM4U-ht3
.

does some one know a quick fix for this - i would be verry thankfull

I still can't find a way to stop Jackett from appending a / to the end of the link @Lauwens sent:

This might help:
https://horriblesubs.info/api.php?method=getlatest

Any ideas anyone?
Jackett changes the above URL to https://horriblesubs.info/api.php?method=getlatest/ which doesn't work.

There is heaps of devs that have posted/viewed this issue. Its not a massive task to implement a tracker and there is heaps of examples in https://github.com/Jackett/Jackett/tree/master/src/Jackett.Common/Indexers to copy from. Community assistance needed

@64Hz https://horriblesubs.info/api.php?method=getlatest# and https://horriblesubs.info/api.php?method=getlatest#/ both work - so mabye just slap a # on the end and see if that works?

also - https://horriblesubs.info/api.php?method=getlatest&nextid=[0-2] will get more results, you can also leave nextid blank to get the default most recent returns - I assume there's normally more than 10-15 results returned by most API's - so might need to do this to make sure none are missed on normal sync times - thanks to whoever picks this up.

I'll give that a whirl when able. Thank you!

On Sun, 15 Jul 2018, 20:24 Connor, notifications@github.com wrote:

@64Hz https://github.com/64Hz
https://horriblesubs.info/api.php?method=getlatest# and
https://horriblesubs.info/api.php?method=getlatest#/ both work - so mabye
just slap a # on the end and see if that works?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Jackett/Jackett/issues/3318#issuecomment-405112245,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APSf5CRa1E7KvqOT8GeopU50RezMJ0s2ks5uG5b1gaJpZM4U-ht3
.

@colsw I tested both URL's as my Jackett indexer for HorribleSubs and whilst the URLs work in a browser, Jackett seems to be unable find any releases from it. I will leave it saved and see if that changes when they next release something, but just wanted to let you know.

Bump. Their RSS feed is a useful stopgap. Can't search, but at least you can grab latest releases: https://horriblesubs.info/rss.php?res=all

Also want to comment that their search api method (https://horriblesubs.info/api.php?method=search&value=test&_=1534542892201) doesn't seem to always get the most results.

Might be worth periodically scraping https://horriblesubs.info/shows/ for shows, parsing the show pages (https://horriblesubs.info/shows/made-in-abyss/) for the show ID (<script type="text/javascript">var hs_showid = 924;</script>) to create a cache that can be used for future searches using the getshows api method (https://horriblesubs.info/api.php?method=getshows&type=show&showid=924&nextid=1&_=1534543062011)

Still having this same problem. Note the URL needs to be https:// for anyone else who had issues there.
After that is fixed, it returns:

An error occured while testing this indexer
Found no results while trying to browse this tracker

Actually I have more to add to this:

System.Exception: Found no results while trying to browse this tracker at Jackett.Common.Services.IndexerManagerService+<TestIndexer>d__18.MoveNext () [0x000e8] in C:\projects\jackett\src\Jackett.Common\Services\IndexerManagerService.cs:225 --- End of stack trace from previous location where exception was thrown --- at Jackett.Server.Controllers.IndexerApiController+<Test>d__15.MoveNext () [0x000e1] in C:\projects\jackett\src\Jackett.Server\Controllers\IndexerApiController.cs:141 --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor+TaskOfIActionResultExecutor+<Execute>d__0.MoveNext () [0x00071] in <703e2bb4fd86407aa6c8a21fddb328a9>:0 --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker+<InvokeActionMethodAsync>d__12.MoveNext () [0x00131] in <703e2bb4fd86407aa6c8a21fddb328a9>:0 --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker+<InvokeNextActionFilterAsync>d__10.MoveNext () [0x0009e] in <703e2bb4fd86407aa6c8a21fddb328a9>:0 --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow (Microsoft.AspNetCore.Mvc.Filters.ActionExecutedContext context) [0x0001b] in <703e2bb4fd86407aa6c8a21fddb328a9>:0 at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next (Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker+State& next, Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker+Scope& scope, System.Object& state, System.Boolean& isCompleted) [0x00382] in <703e2bb4fd86407aa6c8a21fddb328a9>:0 at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker+<InvokeInnerFilterAsync>d__13.MoveNext () [0x0002f] in <703e2bb4fd86407aa6c8a21fddb328a9>:0 --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+<InvokeNextResourceFilter>d__23.MoveNext () [0x0009f] in <703e2bb4fd86407aa6c8a21fddb328a9>:0 --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow (Microsoft.AspNetCore.Mvc.Filters.ResourceExecutedContext context) [0x0001b] in <703e2bb4fd86407aa6c8a21fddb328a9>:0 at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next (Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+State& next, Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+Scope& scope, System.Object& state, System.Boolean& isCompleted) [0x00840] in <703e2bb4fd86407aa6c8a21fddb328a9>:0 at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+<InvokeFilterPipelineAsync>d__18.MoveNext () [0x0002f] in <703e2bb4fd86407aa6c8a21fddb328a9>:0 --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+<InvokeAsync>d__16.MoveNext () [0x0012e] in <703e2bb4fd86407aa6c8a21fddb328a9>:0 --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Builder.RouterMiddleware+<Invoke>d__4.MoveNext () [0x001cb] in <0c4aed80d53349aab59d38ff83ba08f0>:0 --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware+<Invoke>d__6.MoveNext () [0x00384] in <f5622e7f79be469e83d9e2bde9addd07>:0 --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware+<Invoke>d__7.MoveNext () [0x0043e] in <6ec74abaae414d0a97ef0613561299ae>:0 --- End of stack trace from previous location where exception was thrown --- at Jackett.Server.Middleware.CustomExceptionHandler+<Invoke>d__3.MoveNext () [0x00042] in C:\projects\jackett\src\Jackett.Server\Middleware\CustomExceptionHandler.cs:29

If you are using this for Sonarr, an alternative at this point is to search another tracker (like nyaa or nyaa-pantsu) for releases containing [HorribleSubs].

I've been doing what Austin suggested above and it has worked well.
You can specify within sonar to search for Specific strings in releases
based on tags within sonarr.

E.g. I have tagged Tokyo Ghoul with hs and it will search directly for
[Horrible subscribe] to be included in the torrent title.

On Wed, 5 Sep 2018, 23:43 Austin Jackson, notifications@github.com wrote:

If you are using this for Sonarr, an alternative at this point is to
search another tracker (like nyaa
https://github.com/Jackett/Jackett/blob/master/src/Jackett.Common/Definitions/nyaasi.yml
or nyaa-pantsu
https://github.com/Jackett/Jackett/blob/master/src/Jackett.Common/Definitions/nyaa-pantsu.yml)
for releases containing [HorribleSubs].

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Jackett/Jackett/issues/3318#issuecomment-418905105,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APSf5BRXDFQM-UeRgLALO39X1vlUFVY-ks5uYFOdgaJpZM4U-ht3
.

@au5ton @64Hz Thanks that's a great workaround

Thanks to @gerdus this is now back in the latest release

@gerdus @flightlevel
This doesn't seem to work for me in sonarr on 0.10.178.0
The sonarr log reads:
[v2.0.0.5228] NzbDrone.Core.Indexers.Torznab.TorznabException: Torznab error detected: horriblesubs does not support the requested query. Please check the capabilities (t=caps) and make sure the search mode and categories are supported.

I'm guessing this is because t=caps returns

<?xml version="1.0" encoding="UTF-8"?>
<caps>
  <server title="Jackett" />
  <searching>
    <search available="yes" supportedParams="q" />
    <tv-search available="yes" supportedParams="q,season,ep" />
    <movie-search available="no" supportedParams="q" />
    <music-search available="no" supportedParams="" />
    <audio-search available="no" supportedParams="" />
  </searching>
  <categories />
</caps>

And sonarr doesn't like the lack of categories?

@kaysond try latest version of Jackett

@flightlevel fixed! thanks

Was this page helpful?
0 / 5 - 0 ratings