starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Conflicting messages regarding UPnP port mapping failed, no router found #14691

New issue

Open

opened 2026-02-22 01:19:54 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-22 01:19:54 -05:00

Owner

Originally created by @nokti on GitHub (Jun 9, 2023).

qBittorrent & operating system versions

qBit v4.5.3 x64
OS: Windows 10 Pro (10.0.1xxxx)
Qt: 6.5.1
Lib: 2.0.9

What is the problem?

I'm getting conflicting messages regarding upnp port mapping.

This is what I get when I first launch qBit:

And after several minutes:

I don't have a router. Just a cable straight from my computer to the adsl modem. But the conflicting messages given by qBit makes me wonder what's going on and if I should do something about it.

Steps to reproduce

No response

Additional context

No response

Log(s) & preferences file(s)

No response

Originally created by @nokti on GitHub (Jun 9, 2023). ### qBittorrent & operating system versions qBit v4.5.3 x64 OS: Windows 10 Pro (10.0.1xxxx) Qt: 6.5.1 Lib: 2.0.9 ### What is the problem? I'm getting conflicting messages regarding upnp port mapping. This is what I get when I first launch qBit: ![Capture d’écran 2023-06-09 091304](https://github.com/qbittorrent/qBittorrent/assets/58652818/d9e98cab-9fa2-448d-9c58-e20f4ad29827) And after several minutes: ![Capture d’écran 2023-06-09 091338](https://github.com/qbittorrent/qBittorrent/assets/58652818/75a20a04-cda4-4493-8eaf-21d82816ee0a) I don't have a router. Just a cable straight from my computer to the adsl modem. But the conflicting messages given by qBit makes me wonder what's going on and if I should do something about it. ### Steps to reproduce _No response_ ### Additional context _No response_ ### Log(s) & preferences file(s) _No response_

deekerman added the

Documentation

Waiting diagnosis

labels

2026-02-22 01:19:54 -05:00

deekerman commented

2026-02-22 01:20:04 -05:00

Author

Owner

@stalkerok commented on GitHub (Jun 9, 2023):

As far as I know these messages are for different network interfaces.
Don't worry about it.

@stalkerok commented on GitHub (Jun 9, 2023): As far as I know these messages are for different network interfaces. Don't worry about it.

deekerman commented

2026-02-22 01:20:04 -05:00

Author

Owner

@nokti commented on GitHub (Aug 24, 2023):

I have solved this issue by binding to my adsl box IP (in Options > Advanced > Optional IP address to bind to). No more error messages.

@nokti commented on GitHub (Aug 24, 2023): I have solved this issue by binding to my adsl box IP (in Options > Advanced > Optional IP address to bind to). No more error messages.

deekerman commented

2026-02-22 01:20:04 -05:00

Author

Owner

@luzpaz commented on GitHub (Sep 7, 2023):

I have solved this issue by binding to my adsl box IP (in Options > Advanced > Optional IP address to bind to). No more error messages.

@nokti thanks for the follow-up. Any idea why that worked ?

@luzpaz commented on GitHub (Sep 7, 2023): > I have solved this issue by binding to my adsl box IP (in Options > Advanced > Optional IP address to bind to). No more error messages. @nokti thanks for the follow-up. Any idea why that worked ?

deekerman commented

2026-02-22 01:20:04 -05:00

Author

Owner

@nokti commented on GitHub (Sep 9, 2023):

@luzpaz No idea. I think this issue only affected qBit since at least v4.5.3. I switched to IP binding because I was told on a private tracker that I shouldn't be announcing the same info over multiple IP addresses. After doing that I realized that it also solved this issue.

@nokti commented on GitHub (Sep 9, 2023): @luzpaz No idea. I think this issue only affected qBit since at least v4.5.3. I switched to IP binding because I was told on a private tracker that I shouldn't be announcing the same info over multiple IP addresses. After doing that I realized that it also solved this issue.