Help and Support
Ask a question, report a problem, request a feature...
<<  Back To Forum

Error Reading meta-file : the system cannot find the file specif

by Guest on 2019/12/14 08:21:05 AM    
I'm getting this message every time i try to DL a new torrent file, I've used Tixati for years and haven't had this issue as of yet. Im using Iptorrents and PIA if that makes a difference.
by Guest on 2019/12/15 10:44:11 PM    
I am also having this issue, just started as of 15 Dec 19.
by Guest on 2019/12/18 06:00:21 PM    
Hello everyone.

Like this:
https://ibb.co/4Vw1M4Q    ???

This downloads from one torrent file.
by Guest on 2019/12/18 07:25:57 PM    
Hello everyone.

Like this:
https://ibb.co/4Vw1M4Q     ???

This downloads from one torrent file.
This problem was solved by simply renaming the torrent-file with russian symbols to 1.torrent.
But all early versions of the program up to 2.63 work quietly with russian symbols in torrent-file name.
by Guest on 2019/12/19 07:18:38 PM    
This problem was solved by simply renaming the torrent-file with russian symbols to 1.torrent.
But all early versions of the program up to 2.63 work quietly with russian symbols in torrent-file name.

post the torrent name and the magnet-link of the torrent. it will get sent to the devs and fixed.
by Guest on 2020/01/01 05:07:27 PM    
My torrent file does not have any russian symbols. Working as necessary with double click after separately downloading it, but via any browser the same thing is seen in the picture above. What to do?
by Guest on 2020/01/07 03:20:19 AM    
It's happening to me as well.  It's literally every torrent I try to download.  I've tried from multiple sources and multiple media types.  It started right after I ran an update.

What info would be helpful?
by Guest on 2021/12/27 11:46:53 AM    
Settings > Transfers > Meta-info > Delete .torrent files immediately...
Remove the folder path
by Guest on 2023/11/18 08:33:41 AM    
Settings > Transfers > Locations

Make sure that all the paths are valid.
I started having this problem, upgraded ... etc ...
Ended up being I had the "Upon completion move to" set to a drive that was no longer on the system.
Changed the "Upon completion move to" to a valid drive/dir and all works fine now.




This web site is powered by Super Simple Server