Comments

You must log in or register to comment.

Rambler said ()

I'm responding to this from ramble.i2p right now, are you still experiencing this?

What I2P subscription lists are you using in https://127.0.0.1:7667/dns ?

For example, mine looks like:

http://identiguy.i2p/hosts.txt
http://notbob.i2p/hosts-all.txt
http://skank.i2p/hosts.txt
http://stats.i2p/cgi-bin/newhosts.txt
1

dhritimitra OP said ()

Sorry for the late reply, I forgot about this. I'm still having the same problem, looks more worse, because now I can't even open the homepage (tried both B32 and ramble.i2p). Replying this from ramble.pw using an i2p outproxy

I use i2pd. My subscriptions are the default: http://reg.i2p/hosts.txt http://identiguy.i2p/hosts.txt http://stats.i2p/cgi-bin/newhosts.txt http://i2p-projekt.i2p/hosts.txt

My bandwidth is set to 32KB/s (class L) with 80% of it on share. I have restricted the number of transit tunnels to 1 (my internet plan is limited, 2GB/day) But these shouldn't matter because I can open every other eepsite perfectly fine, be it Dread, reg.i2p, stats.i2p, IRCs, various chans, tube.i2p, libreddit.i2p, etc etc

1

BlueHat said ()

That happens with many other eepsites for me. Since it happens to some sites more frequently than others, I'd assume that it's related to geolocation / (how far the server is away from you). I'm not an I2P expert, but the whole tunneling part seems rather complex and prone to latency issues due to possible problems with intermediate routers, so maybe ramble doesn't always resolve properly because of something going wrong in the middle of the connection.

1