I did a try to Tixati, then I had to come back to qbittorrent. The reason is qbittorrent works with my Sagemcom router upnp and Tixati don't.

It does not open the requested port automatically and no error message given. So often peers can't connect and so the need to come back to qbittorrent.

I can see a upnp_diagnostic_log.txt in my user\appdata\roaming\tixati folder but this file is always ZERO bytes.

If someone can help or developer is interested in this problem, I can send additional information.

I repeat, upnp works fine here with other clients.

If this problem will be fixed I will more than happy to give Tixati another chance becouse overall I like it.

Make sure Tixati is added to your firewall's exception list, and that you are not using the same port number with another program.

Thank you for your reply.

I double checked forward rules in Windows Firewall and they are ok.

I even deleted everything and let Tixati ask me again to create it.

If I manually forward the port, I'm sure it will work. Sadly, I can't manually forward ports on this machine and so I have to relay on upnp.

And that is where the problem, IMHO, is.

Still there is a zero byte file in the appdata tixati folder related with the upnp log. It's like if this part of the code doesn't work on my machine.

And it is just a problem with Tixati becouse I do have many other rules on my Sagemcom modem created by upnp (included qbittorrent) and they all works fine. What can I do is to allow qbittorrent or any other app to open the port and then configure Tixati to use them. Then, I think this is not the right way to use the program.

Now, reading the very well done help support on Tixati site, I can see pictures related with the network configuration/incoming that are no more actual, in this new version.

There is no option to manually force a configuration and there is no option to individually choose type of ports and ports number.

It is like if this support is now a lot less accurate.

If you need more info, just ask.

I would post screenshots, but it seams to me the forum doesn't allow me to do that.

A lot of cheap routers implement UPnP via some nonsensical XML concatenation hacks probably written by some embedded Linux freelancer in 2005. It is not uncommon to see something work with one tool or program, and break with another. Both send requests according to the standard, but the parser on the router is simply broken.

Still, you can use Help menu (question button), then Diagnostics, then UPnP/NAT-PMP Log. If there is something suspicious, you can copy the log to upload it to some pastebin site.

To set the port, go to Settings, Network, Incoming Ports. Set a specific port number (not used by anything else on your system(s)). There's also a checkbox to use UPnP/NAT-PMP, I assume it is already set. If it's not, we found your problem. There's also a time period to switch ports, turn it off. Then try to use Windows built-in UPnP controller. In Explorer, choose Network. UPnP-enabled router should be shown there. Open its properties, then click on Settings. You should be able to add ports to forward there through Windows UPnP implementation, which might or might not be more compatible with your router, even without access to its main web interface for all configuration.

I suggest getting a new WiFi box which has better security as well as better firmware

Be wary that some ISPs are blocking torrents using Sandvine and other attacks

Hello Anoid, and thankx for your reply. Just, you didn't read my previous posts: ISP DO NOT BLOCK torrent and OTHER clients works fine.

No, another router considering what I said before, just to eventually properly run Tixaty, is not an option considering I do not have problems with ALL the others Torrent clients I try.

I was interested in Tixati becouse I like the interface and it look promising to me, a really complete client, with a lot of infos, then upnp just doesn't work for me.


I did a try on another box with another router and another ISP (router ZyXEL this time) and in this case upnp seems to work: it open the ports. Then when I do check if the ports are properly open using a public port scanner like IPVoid (for UDP) or Port Checker (for TCP), the ports seems closed and also DHT infos on Tixati bottom bar complain there is a problem with DHT nodes. On this box, then, it seems to download faster compared to the other, then DHT figure is still too little IMHO.

If I manually open this ports, everything is fine (DHT nodes double in number). So, yes, two out of two, I think Tixati has problems with upnp implementation.

So I maybe come back in a year or so to see if it is solved. For now, I let go and I happily stay with another client (they all works fine with upnp).

*** 24/05/2025 ***
[0.09.01]  in ascolto tcp:0.0.0.0:28202
[0.09.01]  in ascolto tcp:[::]:28202
[0.09.01]  in ascolto udp:0.0.0.0:28202
[0.09.01]  in ascolto udp:[::]:28202
[0.09.04]  mappatura NAT-PMP porta TCP 28202 sul gateway 192.168.1.1 - socket error waiting for rispondere: Connection ripristina (10054)
[0.09.05]  UPNP mappato porta TCP 28202 sul gateway 192.168.1.1
[0.09.05]  mappatura NAT-PMP porta UDP 28202 sul gateway 192.168.1.1 - socket error waiting for rispondere: Connection ripristina (10054)
[0.09.06]  UPNP mappato porta UDP 28202 sul gateway 192.168.1.1

Hello this is another report on another machine with another gateway.

This upnp on Router Sagemcom is named on the router configuration page: UPNP IGd and it works pretty fine with every other program, example related with torrent clients I tried   BiglyBT and Bitcomet and they all correctly open the configured upnp ports.

In the case of Tixati the log is this:

0.31.27]  UPNP mapping UDP port 28202 on gateway 192.168.1.254 - searching for service:WANPPPConnection:1
[0.31.27]  UPNP mapping UDP port 28202 on gateway 192.168.1.254 - sending to 192.168.1.254:1900
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 3
ST: urn:schemas-upnp-org:service:WANPPPConnection:1


[0.31.27]  UPNP mapping UDP port 28202 on gateway 192.168.1.254 - searching for service:WANPPPConnection:1
[0.31.27]  UPNP mapping UDP port 28202 on gateway 192.168.1.254 - sending to 239.255.255.250:1900
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 3
ST: urn:schemas-upnp-org:service:WANPPPConnection:1


[0.31.28]  UPNP mapping UDP port 28202 on gateway 192.168.1.254 - no UPNP services found on network
[0.31.28]  UPNP mapping UDP port 28202 on gateway 192.168.1.254 - no UPNP services found on network

I think the problem is with Tixati: out of two gateway of two different Service Providers all the other apps (not just Torrent clients, everything) works with upnp but Tixati .

If you need more info, I'm here, I consider Tixati very interesting but - we have to admit it - upnp is seriously broken, for now I can say with ZyXEL and Sagemcom gateways.

Those companies have probably made more than one model of a home router with very different hardware and software.

Yeah, I have the same problem. Other torrent clients work fine...
My router is a Huawei B311-221.

[20:29:18]  UPNP mapping UDP port 61372 on gateway 192.168.1.1 - got HTTP response code 500
[20:29:18]  UPNP mapping UDP port 61372 on gateway 192.168.1.1 - got reply:
<s:Envelope
xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<s:Fault>
<faultcode>s:Client</faultcode>
<faultstring>UPnPError</faultstring>
<detail>
<UPnPError xmlns="urn:schemas-upnp-org:control-1-0">
<errorCode>402</errorCode>
<errorDescription>Invalid Args</errorDescription>
</UPnPError>
</detail>
</s:Fault>
</s:Body>
</s:Envelope>

[20:29:18]  UPNP mapping UDP port 61372 on gateway 192.168.1.1 - command failed with error 402 Invalid Args
[20:29:18]  UPNP mapping UDP port 61372 on gateway 192.168.1.1 - command failed with error 402 Invalid Args
[20:29:18]  UPNP mapping UDP port 61372 on gateway 192.168.1.1 - command failed with error 402 Invalid Args
[20:29:18]  mapping UDP port 61372 on gateway 192.168.1.1 will be retried every 5 minutes
[20:29:18]  mapping UDP port 61372 on gateway 192.168.1.1 will be retried every 5 minutes