Opened 10 years ago

Closed 10 years ago

#1476 closed defect (WorksForMe)

Error: invalid port

Reported by: kyle12 Owned by:
Priority: blocker Milestone: 1.3.2
Component: Core Version: 1.3.1
Keywords: Cc:

Description

So basically every time that I use a tracker without a specified port in the tracker URL. Deluge says "Error: invalid port".

I've marked this as a blocker. I haven't tried adding this torrent through anything else besides the WebUI. So it could be an issue with the extremely buggy WebUI.

Attachments (1)

debugoutput.txt (1.8 KB) - added by kyle12 10 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 10 years ago by damoxc

Attaching logs would be a useful start as no one else has had this happen to them. I have been happily using the web interface for months, adding torrents via url and file and auto-add without experiencing this, so logic suggests its something specific to your environment.

Please refer to the FAQ if you don't know how to turn on logging.

comment:2 Changed 10 years ago by kyle12

[INFO ] 02:29:07 torrentmanager:476 Torrent TORRENTNAME added by user: localclient [DEBUG ] 02:29:07 alertmanager:123 torrent_resumed_alert: TORRENTNAME resumed [DEBUG ] 02:29:07 alertmanager:123 state_changed_alert: TORRENTNAME: state changed to: downloading [DEBUG ] 02:29:07 alertmanager:123 torrent_checked_alert: TORRENTNAME checked [DEBUG ] 02:29:07 alertmanager:123 tracker_announce_alert: TORRENTNAME (http://TrackerName.org/announce.php?passkey=MyPasskey) sending announce (started) [DEBUG ] 02:29:07 torrentmanager:919 on_alert_torrent_resumed [DEBUG ] 02:29:07 torrent:351 set_state_based_on_ltstate: Downloading [DEBUG ] 02:29:07 torrent:352 session.is_paused: False [DEBUG ] 02:29:07 rpcserver:466 intevents: {2: ['TorrentRemovedEvent?', 'PluginEnabledEvent?', 'TorrentAddedEvent?', 'PluginDisabledEvent?', 'TorrentStateChangedEvent?', 'ConfigValueChangedEvent?']} [DEBUG ] 02:29:07 rpcserver:470 Emit Event: TorrentStateChangedEvent? ['Removed', 'Downloading'] [DEBUG ] 02:29:07 rpcserver:466 intevents: {2: ['TorrentRemovedEvent?', 'PluginEnabledEvent?', 'TorrentAddedEvent?', 'PluginDisabledEvent?', 'TorrentStateChangedEvent?', 'ConfigValueChangedEvent?']} [DEBUG ] 02:29:07 torrentmanager:934 on_alert_state_changed [DEBUG ] 02:29:07 torrent:351 set_state_based_on_ltstate: Downloading [DEBUG ] 02:29:07 torrent:352 session.is_paused: False [DEBUG ] 02:29:07 torrentmanager:847 on_alert_torrent_checked [DEBUG ] 02:29:07 torrent:351 set_state_based_on_ltstate: Downloading [DEBUG ] 02:29:07 torrent:352 session.is_paused: False [DEBUG ] 02:29:07 torrentmanager:881 on_alert_tracker_announce [DEBUG ] 02:29:08 alertmanager:123 tracker_error_alert: TORRENTNAME (http://TrackerName.org/announce.php?passkey=MyPasskey) (200) invalid port (1) [DEBUG ] 02:29:08 torrentmanager:901 on_alert_tracker_error

Trackers with Ports ie http://TrackerName.org:30000/Whatever work. However Portless trackers fail with the above. I've tested on multiple sites, and multiple torrents.

Changed 10 years ago by kyle12

comment:3 Changed 10 years ago by kyle12

Any update on this?

comment:4 Changed 10 years ago by andar

  • Resolution set to worksforme
  • Status changed from new to closed

This could be a problem with the tracker itself. If you don't believe it is, please file this bug with libtorrent at http://www.libtorrent.org

Note: See TracTickets for help on using tickets.