Jump to content
Comet Forums

Search the Community

Showing results for tags 'tracker connection'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • New Members' Report!
  • BitComet
    • BitComet General Discussion
    • Guides and Tutorials
    • VIP Acceleration
    • BitComet Bug Reports
    • BitComet Feature Requests
    • Incomplete and Deleted Topics
  • BitComet International (Non-English)
    • Español (Spanish Members)
    • Français (French members)
    • Romana (Romanian Members)
    • Japanese Forum
    • BitComet Translations
  • CometBird & CometMarks
    • CometBird General Discussions
    • CometMarks General Discussion
  • Video Playback
    • MPCStar General Discussions
    • CometPlayer General Discussions
  • Others
    • Torrent Questions
    • General Questions
    • Lounge

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Hello BitComet team, I recently updated BitComet 1.49 -> 1.52 (I regret it). I haven't any problem with BitComet 1.49. Now, with BitComet 1.52 I have a big bug with one tracker particurlarly : yggtorrent.to (tracker.ygg.is) When I download a new torrent, all is good, I can leech, finish my download then seed my torrent. I can stop, and start again the task. But, each time I close BitComet, when I start BitComet again, all my torrents from this tracker only, don't connect again from this tracker... The event log of the torrent is : "No log found for this tracker"... there isn't any "Announce START : http://tracker.ygg.is" Consequently, BitComet can't resume the download, or seeding the torrent... If I delete the torrent, and download it again, the connexion of the tracker is OK, and BitComet connects from other peers... I tried to uninstall BitComet 1.52 and go back to BitComet 1.49, but, oddly, BitComet has the same behavior... weirdly too, the line DHT IPv6 network is still present. Thanks to fix quickly this bug. Regards, JmK
×