with i2pd I get no errors from tixati but the trackers always time out and the i2pd console shows no sam connection
with the i2p java client tixati errors with "bad i2p session create (51467)" trackers always time out too
ports seem to be correct with both clients

Can confirm, at least on 32-bit Tixati 3.32 on Windows 10. Tested both upgraded client with torrents and portable with clean database.

When enabling I2P, or changing settings, Wireshark shows
> HELLO VERSION MIN=3.1 MAX=3.9
from Tixati to port 7656, then
> HELLO REPLY RESULT=OK VERSION=3.1
in return, then complete silence. You can add I2P trackers, remove them, announce manually, and nothing happens. It's always “Waiting for connect”, then “Waiting for I2P router”, then timeout.

I suspect the interface selection logic. If I manually set the client port in I2P settings to 12345, Tixati says in the log that it listens to 127.0.0.1:12345 for I2P connections, but uses port 58600 to exchange “hellos” with the router. If I clean the port number, it outputs port 58631 in the log, but uses 58632 to send messages. Moreover, interface selection menu doesn't have entry for 127.0.0.1, only for ::1. Choosing it results in “address family not available” error at the next attempt. GUID and interface name seem to do nothing. Or maybe it “works” the same way. I vaguely remember that similar interface and alternative port options seemed to be broken in FOPNU in a similar manner: default (unset) configuration worked, trying to set something manually didn't.

good to know its not just me
I also noticed that turning off i2p doesn't remove the trackers, you have to select all torrents and then tick off i2p in the right click menu

When using the original I2P router, the error "Bad I2P session create (51468)" always pops up.
When using I2PD no errors appear, but in tracker statistics the message "Waiting for I2P router" appears is changed to "Timed out - Retry in M:ss."
There are no SAM connections in the router console, neither in the original version nor in Purple.

Also, the purpose of Login/Password in the I2P settings is not clear.

Probably a correction is needed when creating a SAM session

https://i2pforum.net/viewtopic.php?t=1221
https://github.com/qbittorrent/qBittorrent/issues/19625

It can be your I2pd router, i noticed that github channel works better than other channel(debian, windows store), you can find it in releases or actions: https://github.com/PurpleI2P/i2pd/actions/workflows/build-deb.yml  , i use a version from Dec 31 2024. But latest should work.

Now I believe that tracker grouping and on-demand connection logic is super borked.

The only way I can see anything except HELLO on SAM connection is turning I2P mode on AND making all torrents Internet-only AND leaving some .i2p trackers in some torrent. Then Tixati suddenly begins to perform tracker name lookups (successfully), then to connect to them (unsuccessfully, “stream session id main does not exist”, which is true, there were no messages to set it up from the very start of the client). However, there isn't a single active torrent that uses I2P at that moment.

By any chance, are torrent status flags used to define network affinity 64 bit in source code? They might not fit into 32 bit operations.

There is another complain that something (C client library?) might be broken with multiple interfaces, or Wireguard virtual interface driver specifically.

(Links removed by Mod - They did not work)

I do also have a Wireguard tunnel interface as part of Yggdrasil. Routes are default, and should not affect anything, however, it does not have a MAC address (might break some expectations?), and IPv4 address (not used in Yggdrasil) is autoconfigured, with traffic to 169.254.0.0/16 going nowhere.

Does not work on either Windows or Linux, official channel and github, Java-router I2P and Purple I2Pd, local and remote docker-based i2p cloud router. Nothing works, everything described above.
Should not tell here how someone works on Yggdrasil/Wireguard/Secret channels of purple router/anywhere else, it’s a flood bump of theme or lie or not understanding what and how it should work, and anything more.
Does not work for anyone is what you need to know. And it would be good to know when this will be corrected and if it will ever be corrected.

I2P is not working, niether 32bit nor 64bit in windows 10.
I think Tixati devs should check qBittorrent GitHub on how they implemented it

The Dev is working on this and it should be fixed in the next version.