@Xeha
@orignal
Arch
Danny
Irc2PGuest28384
Irc2PGuest4937
Irc2PGuest75631
Irc2PGuest81267
Over1
R4SAS
RN
Strykar
acetone
ahiru
duanin2
eyedeekay
fidoid_
i2potus
ice_juice
itsAMe_
luvme3
mareki2p
n2_
pinotto
poriori
qend-irc2p
r00tobo
r00tobo[2]
rapidash
sexy
uberius
x74a6
yeti
sexy-
my hosted eepsites seem to get a "curl: (52) Empty reply from server" after about ~45minutes of uptime. Restarting i2pd fixes the issue until some time passes again. Im using nginx as the backend webserver, my i2pd router is not floodfill
orignal
check your clock
orignal
"Cause I'm sexy and I know it"
orignal
that's what I see now
sexy-
system clock is right. the website is also working for me right now but I've been playing around with my i2pd router so its current uptime is about 48mins. reinstalled and made some changes im hoping will resolve it
onon_
What problems are you having with 2pd here?
orignal
I thnink he is out of tunnels
onon_
But what doesn't work?
sexy-
my eepsites end up not working after some uptime (it was recently restarted, so working fine right now). my router was originally a floodfill router and disabling that seems to make it last a bit longer. if the issue comes up again I will post a message here
onon_
What version?
onon_
2.60?
sexy-
2.56.0 - updating might fix it lol
onon_
And client?
sexy-
when the issue was happening I tried both i2p+ and i2pd (the same i2pd that hosts the eepsite) and they both failed
orignal
use 2.60
onon_
Sometimes, on the first request, immediately after receiving a leazeSet, the connection may be broken. This is usually corrected by re-querying. Or f5 in the browser.
sexy-
ok ill try updating and refreshing with f5 in the browser if I see the issue again
sexy-
thanks guys