Private trackers

@MakoPC Are you running with a filter? Digging into the logs to find anything that could indicate where the failure occurs and it might be due to a filter rule I have for freeleech only
 
@MakoPC Are you running with a filter? Digging into the logs to find anything that could indicate where the failure occurs and it might be due to a filter rule I have for freeleech only
Yea I am, want to show me your filter?
 
Yea I am, want to show me your filter?
1692732607931.png


1692732650155.png

1692732674792.png

That's all for the filter


And the IRC seems to be working fine, as it only errors out when trying to grab it to push it to the download client:

21:24:03.000DEBUGrelease rejected: error downloading torrent file for release:
 
21:24:07.000TRACEevents: 'PUSH_ERROR' '&{Subject: Message: Event:pUSH_ERROR ReleaseName:Winning.Time.The.Rise.of.the.Lakers.Dynasty.S02E03.The.Second.Coming.1080i.HDTV.DD5.1.H.264-playTV Filter:Freeleech Indexer:fl InfoHash: Size:2530000000 Status:Error Action:QBittorrent ActionType:QBITTORRENT ActionClient:qBittorrent Rejections:[error downloading torrent file for release: Winning.Time.The.Rise.of.the.Lakers.Dynasty.S02E03.The.Second.Coming.1080i.HDTV.DD5.1.H.264-playTV: All attempts fail: #1: metainfo unexpected content type, got HTML expected a bencoded torrent. check indexer keys for fl - Winning.Time.The.Rise.of.the.Lakers.Dynasty.S02E03.The.Second.Coming.1080i.HDTV.DD5.1.H.264-playTV: bencode: syntax error (offset: 0): unknown value type '<' #2: metainfo unexpected content type, got HTML expected a bencoded torrent. check indexer keys for fl - Winning.Time.The.Rise.of.the.Lakers.Dynasty.S02E03.The.Second.Coming.1080i.HDTV.DD5.1.H.264-playTV: bencode: syntax error (offset: 0): unknown value type '<' #3: metainfo unexpected content type, got HTML expected a bencoded torrent. check indexer keys for fl - Winning.Time.The.Rise.of.the.Lakers.Dynasty.S02E03.The.Second.Coming.1080i.HDTV.DD5.1.H.264-playTV: bencode: syntax error (offset: 0): unknown value type '<'] Protocol:torrent Implementation:IRC Timestamp:2023-08-22 19:24:07.140998386 +0000 GMT m=+5010.800379561}'
21:24:07.000DEBUGsending notification for PUSH_ERROR
21:24:07.000ERRORrelease.runAction: error running actions for filter: Freeleech
21:24:07.000ERRORrelease.Process: error running actions for filter: Freeleech


Parts in bold seem relevant
 
Delete the save path, leave it blank it will default to qBittorrent path
 
Delete the save path, leave it blank it will default to qBittorrent path
Still getting this dang error. I really wonder what it could be. Manually going to the torrent and pulling it works so it's not a tracker side permission issue (I joined FL a few days ago)
 
Still getting this dang error. I really wonder what it could be. Manually going to the torrent and pulling it works so it's not a tracker side permission issue (I joined FL a few days ago)

It's not able to get the torrent file. Do you use an API? If so check leading or trailing spaces.
 
It's not able to get the torrent file. Do you use an API? If so check leading or trailing spaces.
It's pulling straight from IRC using AutoBrr's built-in support for FL and I can't find any places where such an oversight could be :confused: I'm going to try setting up a test box on a clean Debian install to see if its somehow related to a config setting I have on the (heavily) tuned seedbox
 
Are you using the correct passkey?

I'm using the one found here: https://[domain].io/irc.php

I have not however registered the bot's username with nickserv, is that needed?

I've registered, let's see
 
The passkey is the one on your https://[domain].io/my.php
Scroll down and you will see, that passkey needs to be put in AutoBrr indexer settings
 
From within AutoBrr itself I can pull the .torrent file so I have no clue what this flippen software is bugging out about smh
 
From within AutoBrr itself I can pull the .torrent file so I have no clue what this flippen software is bugging out about smh
Join their discord and ask, they usually quite quick to respond
 
Top
Sign up to the MyBroadband newsletter
X