Some destinations not connecting via SAM
Posted: 01 Dec 2023 22:26
There's this weird thing going on, i have no idea how it happens.
Some sites, such as i2p-projekt.i2p open fine both on the http proxy and when trying with SAM (testing with netcat). In this case i connect to site over SAM, type the http headers and stuff, and it gives me a reply almost immediately.
Now there are some other sites (i notice this with tracker2.postman.i2p) that work ok with http proxy, but they don't connect with SAM. In this case, after me typing the http headers, it says "STREAM STATUS RESULT=OK" then just waits for a really long time and times out.
During this time, the log has some messages like "warn - Streaming: LeaseSet was not confirmed in 4000 milliseconds. Trying to resubmit" and "error - Streaming: No packets have been received yet".
But if i try to load the site in http proxy (browser), it opens (so it's not like the site is down).
This is some problem that prevents using things like qbittorrent, which uses SAM and seems to contact trackers also via SAM. (more specifically, i tried adding postman's tracker and also some other tracker to the same torrent, and that other tracker worked, while postman's tracker kept timing out all the time).
What could it possibly be? any way to fix?
ps. i use i2pd and have been trying connecting with SAM for some time already; i only tried doing this with java i2p once, and then java sam just gave error with something about unsupported something (when trying connect tracker2)
Edit: java i2p says: "Unsupported encryption options" when connecting to tracker2 via SAM bridge. Also, the whole thing described above, it does not get fixed when i add SIGNATURE_TYPE=7
Some sites, such as i2p-projekt.i2p open fine both on the http proxy and when trying with SAM (testing with netcat). In this case i connect to site over SAM, type the http headers and stuff, and it gives me a reply almost immediately.
Now there are some other sites (i notice this with tracker2.postman.i2p) that work ok with http proxy, but they don't connect with SAM. In this case, after me typing the http headers, it says "STREAM STATUS RESULT=OK" then just waits for a really long time and times out.
During this time, the log has some messages like "warn - Streaming: LeaseSet was not confirmed in 4000 milliseconds. Trying to resubmit" and "error - Streaming: No packets have been received yet".
But if i try to load the site in http proxy (browser), it opens (so it's not like the site is down).
This is some problem that prevents using things like qbittorrent, which uses SAM and seems to contact trackers also via SAM. (more specifically, i tried adding postman's tracker and also some other tracker to the same torrent, and that other tracker worked, while postman's tracker kept timing out all the time).
What could it possibly be? any way to fix?
ps. i use i2pd and have been trying connecting with SAM for some time already; i only tried doing this with java i2p once, and then java sam just gave error with something about unsupported something (when trying connect tracker2)
Edit: java i2p says: "Unsupported encryption options" when connecting to tracker2 via SAM bridge. Also, the whole thing described above, it does not get fixed when i add SIGNATURE_TYPE=7