discuss I2P

Postman tracker not working in qBitorrent since past few days.

First, I thought this was just temporary error but now I think this is a major issue since it has been 3-4 days already.

Rest all trackers are working normally.

This is what it shows

Strange
I just checked right now, Postman is "Working" in qBitTorrent with all my torrents.
I had the same message as you yesterday, but today it works.
you have tried to restart qBitTorrent, it may have lost the SAM connection

COMiX wrote: ↑Mon Jun 09, 2025 6:43 pm Strange
I just checked right now, Postman is "Working" in qBitTorrent with all my torrents.
I had the same message as you yesterday, but today it works.
you have tried to restart qBitTorrent, it may have lost the SAM connection

i think the problem is in i2pd 2.57 because it still shows

cannot reach peer

in my qbittorrent.

the issue is visible in tixati too.

BiglyBT works fine

Have you already tried running BiglyBT via I2Pd for comparison?

lgillis wrote: ↑Tue Jun 10, 2025 2:44 pm Have you already tried running BiglyBT via I2Pd for comparison?

Why would I do that?

BiglyBT has inbuilt java I2P plugin.

provil wrote: ↑Tue Jun 10, 2025 4:37 pm

lgillis wrote: ↑Tue Jun 10, 2025 2:44 pm Have you already tried running BiglyBT via I2Pd for comparison?

Why would I do that?

BiglyBT has inbuilt java I2P plugin.

Perhaps it's because you claimed to have identified a problem with the I2Pd router in three places at once, including cross-posting, without checking for a configuration error with one client or whether the other client works with this router?

Addendum.
Bear with me, I'm not sitting next to you at your workstation, I can't read your mind either, everything I know about the matter I hear from you. And it's sparse, look at your photo above, you can't even see the protocol number behind the > arrow.
You are not the only one here with this router/client configuration, but at the moment you are the only one experiencing this error behavior. As it stands, you have no choice but to try the exclusion procedure. This means that if BBT reaches the tracker with its integrated Java router, as you write, then you switch off its internal router and use the external I2Pd router instead.

I didn't check with the I2Pd router.
Indeed, everything was blocked.'waiting for acceptor...'
I did a forced restart of the I2Pd VM, the same as for qBitTorrent, and it seems to be working now.

A restart often helps if the whole system is stuck. But if the protocol (SAM) is stuck, then all connections should suffer and not just one of four. The last time someone was unable to connect to PaT, it was due to an incorrect address in their address book. This happens more often than you might think. (Although it could not be clarified how the wrong address got into the address book). But in this case every connection to the tracker fails, even via HTTP.

I'm going in your direction to think that something happened with the address book, because I also had a lot of trouble after the updates, and not just with the torrents, but it seems right now