Version 3.3 not connecting #3444

New issue

Closed

opened 2026-02-21 16:46:38 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-21 16:46:38 -05:00

Owner

Originally created by @Delta-Z on GitHub (Dec 3, 2015).

I'm not sure if it's related to me updating to 3.3.0, or any of Windows 10 updates that happened lately, but qBittorrent is no longer able to make any connections, neither for old nor new torrents.

Originally created by @Delta-Z on GitHub (Dec 3, 2015). I'm not sure if it's related to me updating to 3.3.0, or any of Windows 10 updates that happened lately, but qBittorrent is no longer able to make any connections, neither for old nor new torrents.

deekerman closed this issue

2026-02-21 16:46:40 -05:00

deekerman commented

2026-02-21 16:46:44 -05:00

Author

Owner

@SkoricIT commented on GitHub (Dec 4, 2015):

I have the same issue, all torrents stalled forever.

@SkoricIT commented on GitHub (Dec 4, 2015): I have the same issue, all torrents stalled forever.

deekerman commented

2026-02-21 16:46:46 -05:00

Author

Owner

@Lord-Barker commented on GitHub (Dec 4, 2015):

Same issue here as well. All trackers not working, all torrents (old and new) stalled, 0 peers, 0 seeds.

@Lord-Barker commented on GitHub (Dec 4, 2015): Same issue here as well. All trackers not working, all torrents (old and new) stalled, 0 peers, 0 seeds.

deekerman commented

2026-02-21 16:46:46 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Dec 5, 2015):

Look at your logs. If it says that it is listening to "127.0.0.1" then that means you had configured an invalid(or deleted) network interface. The begining of the log will indicate the exact reason.
Up until v3.2.5 if the interface was missing, qbt would happily connect to "Any interface" and that is why you didn't notice. That is a huge security hole. Now, if something is wrong with the configured interface it listens to 127.0.0.1 aka localhost.
(I cannot tell it to not listen to something).

@sledgehammer999 commented on GitHub (Dec 5, 2015): Look at your logs. If it says that it is listening to "127.0.0.1" then that means you had configured an invalid(or deleted) network interface. The begining of the log will indicate the exact reason. Up until v3.2.5 if the interface was missing, qbt would happily connect to "Any interface" and that is why you didn't notice. That is a huge security hole. Now, if something is wrong with the configured interface it listens to 127.0.0.1 aka localhost. (I cannot tell it to not listen to something).

deekerman commented

2026-02-21 16:46:46 -05:00

Author

Owner

@Delta-Z commented on GitHub (Dec 5, 2015):

It was indeed the problem, thanks.
However, I disagree that this is WAI. I never explicitly configured a network interface for qBittorrent (Teredo Tunneling Pseudo Interface?). When I encountered this the app did not give me any indication of the problem, and it was hard for me to find where to fix it.
What I would expect in this case is a helpful error message, ideally prompting me to choose a different interface so I don't have to go digging in "advanced" (which I would not know about since I never changed it there in the first place). Is there a feature request for something like this?

@Delta-Z commented on GitHub (Dec 5, 2015): It was indeed the problem, thanks. However, I disagree that this is WAI. I never explicitly configured a network interface for qBittorrent (Teredo Tunneling Pseudo Interface?). When I encountered this the app did not give me any indication of the problem, and it was hard for me to find where to fix it. What I would expect in this case is a helpful error message, ideally prompting me to choose a different interface so I don't have to go digging in "advanced" (which I would not know about since I never changed it there in the first place). Is there a feature request for something like this?

deekerman commented

2026-02-21 16:46:46 -05:00

Author

Owner

@Lord-Barker commented on GitHub (Dec 10, 2015):

Still haven't solved the issue, but thanks.

@Lord-Barker commented on GitHub (Dec 10, 2015): Still haven't solved the issue, but thanks.

deekerman referenced this issue

2026-02-21 16:50:41 -05:00

[Wishlist] Labels added to API #3559

deekerman referenced this issue

2026-02-21 16:50:41 -05:00