Add by URL and not show ratio
Posted: Sat Oct 15, 2011 8:05 pm
I have the following types of problems. When I try to add a torrent "add by url," so sometimes it works, sometimes not. That is lower than the first two can move the "add via url." While the last can not be moved, so it must first be saved to your computer and add a file.
Is that the last torrent file invalid, and therefore does not work. This error does not matter, time is just a little more than add a file to the "add url by file."
Deluge is a Web UI version 1.3.1.
This models works:
https://www.xxxxxxxx.net/download.php/1 ... =8180b11b8
http://xxxxxxxx.org/torrents.php?action ... qp89b74vbm
And this kind of not
http://www.xxxxxxxxx.org/download.php/377852.torrent
Second problem: One torrent not show my ratio. I find in FAQ topic. Could this be a problem?
"Why isn't my ratio being reported properly?
There are a few reasons your ratio isn't updating properly. If the server is unresponsive, slow, or overloaded, the "event=stopped" message which is required to update your stats may become lost. Similarly, a faulty, experimental, or beta testing a client, may also cause your stats to be misreported. Another possibility is the site may have a different IP associated with your account than the one you sent the "event=stopped" message with. If your client supports DHT and it is enabled any data transfered via these means will not count toward your ratio."
____
gstv
Is that the last torrent file invalid, and therefore does not work. This error does not matter, time is just a little more than add a file to the "add url by file."
Deluge is a Web UI version 1.3.1.
This models works:
https://www.xxxxxxxx.net/download.php/1 ... =8180b11b8
http://xxxxxxxx.org/torrents.php?action ... qp89b74vbm
And this kind of not
http://www.xxxxxxxxx.org/download.php/377852.torrent
Second problem: One torrent not show my ratio. I find in FAQ topic. Could this be a problem?
"Why isn't my ratio being reported properly?
There are a few reasons your ratio isn't updating properly. If the server is unresponsive, slow, or overloaded, the "event=stopped" message which is required to update your stats may become lost. Similarly, a faulty, experimental, or beta testing a client, may also cause your stats to be misreported. Another possibility is the site may have a different IP associated with your account than the one you sent the "event=stopped" message with. If your client supports DHT and it is enabled any data transfered via these means will not count toward your ratio."
____
gstv