cumlord wrote: ↑Tue Jun 10, 2025 5:52 am
oops, that's what i get for skimming. router integration isn't the issue here then, that looks more like an error message, could have more to do with your browser setup. not able to replicate it here using librewolf
the other thread on the tracker issue/qbittorrent could be along those lines though, usually "can't reach peer" means there's a fail on address lookup (unless it means something different there with qbittorrent), either not in addressbook or not able to find the leaseset. not seen this particular issue as of late either but i don't use the i2pd/qbittorrent setup so could be missing something
No, post 258 is also not the issue.
I firmly believe now that it is i2pd version 2.57 creating this problem I do not know why? But qbittorrent was working fine with older I2PD version. I will check again in this regard.
I use Firefox browser with
idk I2P in private browsing add-on
I am not able to access i2pforum, ticket manager of postman.
I have not changed anything in the address book or lease set as I have just updated i2pd normally.
no settings were tinkered with regarding tunnels, reload tunnel config or any other possible settings.
The major issue is that when I upload torrents it does not get registered into postman due to postman not able to connect, which in turn means either I have to use I2PSnark or BiglyBT.
I read somewhere that Tixati is also facing this issue, so I think it is either postman problem or it is i2pd problem or it is qbittorrent problem.
But it cannot be postman problem because BiglyBT and I2PSnark works fine.
It does not look like qbittorrent problem because rest of the trackers work absolutely fine.
So, only thing left is I2PD