bryter wrote:Can you tell me how do i tell deluge to download series Treme, episodes s02e01 and onwards? in utorrent this is usually done by writing "s02e01-" in the episode number field.
There is not smart filtering, but if you simply want all the episodes of season 2 you can use "Treme.*s02e\d{2}". "\d{2}" means to match exactly two integers.
So i can not start downloading from a specific episode? Only the whole season? What if i want to download episode 5 up to the last episode of season 2?
Also, do i need to make any other changes to the term you provided? If i wanted to download HDTV 720p only, how would i fit it in the expression?
I've started implementing some smart filtering, but it's not ready yet. So matching from episode 5 will require some tricky regex hacking.
You can add custom lines in the subscription dialog to test what matches the expression.
This will match HDTV followed by 720p: "Treme.*s02e\d{2}.*HDTV.*720p"
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.
bro wrote:
That makes no sense. With no cookies you shouldn't have access to the feed. If you open the feed in the browser where you haven't logged in, do you still see the feed?
Are you trying this only on your seedbox, or have you tried running the daemon locally as well?
I figured out why you could access the feed, but not the torrents; you don't enforce SSL in your tracker preferences. Forcing SSL requires cookies for viewing the feed as well.
I'm adding functionality so that you can view the content of the page that you're redirected to when you can't access the torrents.
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.
I want to download filesize <3G .torrent but I can't set the filter right...
I set
(1|2|3).\d{2} GB]
but it will contain xxxxx[12.** GB] not I want
Could anyone help me ?
thx !
For these titles it should work adding "[" at the beginning, like, this: \[(1|2|3).\d{2} GB]
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.
UPDATE: This is fixed!! -- Not sure what was wrong but I just erased the RSS feed from YaRSS2 and re-made it fresh from scratch and it started working. No idea what happened or why this was not working.
Hi everyone, it seems that this is the "official" YARSS2 help thread. I can make my own thread if needed >.<
My problem is this: Feeds are not being added to deluged
Both the seedbox and the thinclient is deluge 1.3.3
I have YaRSS2-1.1.3-py2.7.egg installed on the debian seedbox itself, It shows up in the plugin list however will NOT allow me to keep it checked. It checks, hit apply, ok. Then next time I open the preferences it is unchecked. I have tried many different versions of this egg in the past but all python 2.7 because that is what my python version is.
On my windows machine (thinclient) it's 2.6 egg of course. IT IS showing up, and fetching the feed properly only from the thinclient (except it wont add to torrent queue)!!
My filter is fetching the feed, and showing the green check mark properly next to clients in the feed. One peculiar thing was that even if I "right click" and select "add to queue now" on the feed item, it won't add to the queue.
Keep in mind the configurations that I am setting on the thinclient ARE properly showing in my yarss2.conf file! -- So there is proper communication between the client/server at least with the settings.
Any help is appreciated as I think there is just something simple that I am doing wrong here. I think the issue is that on the WebUI the checkbox is unchecking itself next to the YaRSS2 plugin so whatever is causing that is probably the issue.
EDIT: I enabled logging and Yarss is starting properly!!
the error I am getting is this:
[ERROR ] 20:17:57 logger:70 YaRSS2.torrent_handling:68: Unable to decode torrent file! (invalid bencoding)
senseiz wrote:UPDATE: This is fixed!! -- Not sure what was wrong but I just erased the RSS feed from YaRSS2 and re-made it fresh from scratch and it started working. No idea what happened or why this was not working.
Hi everyone, it seems that this is the "official" YARSS2 help thread. I can make my own thread if needed >.<
My problem is this: Feeds are not being added to deluged
Both the seedbox and the thinclient is deluge 1.3.3
I have YaRSS2-1.1.3-py2.7.egg installed on the debian seedbox itself, It shows up in the plugin list however will NOT allow me to keep it checked. It checks, hit apply, ok. Then next time I open the preferences it is unchecked. I have tried many different versions of this egg in the past but all python 2.7 because that is what my python version is.
On my windows machine (thinclient) it's 2.6 egg of course. IT IS showing up, and fetching the feed properly only from the thinclient (except it wont add to torrent queue)!!
My filter is fetching the feed, and showing the green check mark properly next to clients in the feed. One peculiar thing was that even if I "right click" and select "add to queue now" on the feed item, it won't add to the queue.
Keep in mind the configurations that I am setting on the thinclient ARE properly showing in my yarss2.conf file! -- So there is proper communication between the client/server at least with the settings.
Any help is appreciated as I think there is just something simple that I am doing wrong here. I think the issue is that on the WebUI the checkbox is unchecking itself next to the YaRSS2 plugin so whatever is causing that is probably the issue.
EDIT: I enabled logging and Yarss is starting properly!!
the error I am getting is this:
[ERROR ] 20:17:57 logger:70 YaRSS2.torrent_handling:68: Unable to decode torrent file! (invalid bencoding)
"Unable to decode torrent file" means that the downloaded content is not a torrent file. If you are denied access to the address (e.g. redirected to an error page), this could happen.
The next version will show you the content of the failed download, which often is a html page with some comment.
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.
deluge -l deluge.log -L info
deluged -l deluge.log -L info
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.
<USER>@<NAS>:~$ cat deluge.log
[INFO ] 11:52:30 daemon:129 Deluge daemon 1.3.5
[INFO ] 11:52:31 core:80 Starting libtorrent 0.15.10.0 session..
[WARNING ] 11:52:31 core:173 Failed to load lt state: [Errno 2] No such file or directory: '/home/<USER>/.config/deluge/session.state'
[WARNING ] 11:52:31 config:361 Unable to open config file /home/<USER>/.config/deluge/core.conf: [Errno 2] No such file or directory: '/home/<USER>/.config/deluge/core.conf'
[INFO ] 11:52:31 rpcserver:366 Starting DelugeRPC server localhost:<PORT>
[WARNING ] 11:52:31 preferencesmanager:303 Unable to read DHT state file: [Errno 2] No such file or directory: '/home/<USER>/.config/deluge/dht.state'
[WARNING ] 11:52:31 torrentmanager:630 Unable to update state file to a compatible version: list index out of range
[WARNING ] 11:52:31 torrentmanager:733 Unable to load fastresume file: [Errno 2] No such file or directory: '/home/<USER>/.config/deluge/state/torrents.fastresume'
<USER>@<LAPTOP>:~$ cat deluge.log
[INFO ] 12:07:13 main:125 Deluge ui 1.3.5
[INFO ] 12:07:13 main:131 Starting ui..
[INFO ] 12:07:13 ui:148 Starting GtkUI..
[WARNING ] 12:07:13 gtkui:186 Unable to register a 'die' handler with the GNOME session manager: No module named gnome.ui
[INFO ] 12:07:14 client:221 Connecting to daemon at 127.0.0.1:<PORT>..
[INFO ] 12:07:14 client:221 Connecting to daemon at <IPADDRESS>:<PORT>..
[INFO ] 12:07:14 client:221 Connecting to daemon at <IPADDRESS>:<PORT>..
[WARNING ] 12:07:14 client:224 Connection to daemon at 127.0.0.1:<PORT> failed: Connection was refused by other side: 111: Connection refused.
[INFO ] 12:07:14 client:125 Connected to daemon at <IPADDRESS>:<PORT>..
[INFO ] 12:07:15 client:228 Connection lost to daemon at <IPADDRESS>:<PORT> reason: Connection was closed cleanly.
[WARNING ] 12:07:15 client:224 Connection to daemon at <IPADDRESS>:<PORT> failed: Connection was refused by other side: 111: Connection refused.
=============================================================== Server: Rock 5B 8 Cores (ARM), 16 GB RAM, 2 TB 970 Evo + OS: Linux Ubuntu 24.04 LTS Deluge: v2.1.2 Plugins: Blocklist, LabelPlus, ItConfig, MyScheduler, Stats, Notifications, YaRSS2
shinger, in the log it says "Address already in use". That means the daemon is already running and occupying that address/port. You need to stop deluged before starting it with logging enabled.
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.