IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2023/03/08
@eyedeekay
&eche|on
&zzz
+Irc2PGuest81845
+R4SAS
+RN
+StormyCloud
+acetone
+cumlord
+dr|z3d
+eche|off
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch2
Birdy
BubbRubb
Chrono
Daddy
Dann
DeltaOreo
Irc2PGuest27269
Irc2PGuest53924
Irc2PGuest65801
Irc2PGuest74254
Irc2PGuest90985
Irc2PGuest92550
Irc2PGuest95708
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
SlippyJoe
Stormycloud_
T3s|4_
Teeed
aargh2
ac9f_
anontor
b3t4f4c3__
dr4wd3
duanin2
duck
eyedeekay_bnc
gellegery
makoto
matean
n1
nilbog
not_bob_afk
null912
onon_
poriori
profetikla
r00tobo_BNC
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
x74a6
xHarr
mesh dr|z3d: purokishi.i2p is still down?
dr|z3d never was, mesh.
mesh dr|z3d: I get Website Unreachable errors when I go to purokishi.i2p. When I go to other sites I get "Outproxy Not Found"
dr|z3d try restarting your http proxy tunnel.
dr|z3d if you're on 0-hop, increase to 1-hop.
RN did you look in the tunnel manager? there was a typo a little while ago
mesh dr|z3d: I'll restart the router, but why does this happen? Why do outproxies just become...unsuable until a router restart?
dr|z3d no need to restart the router.
dr|z3d just try restarting you http proxy tunnel.
mesh hmm. restarting I2P HTTP Proxy doesn't help
mesh but something is up. the tunnel is stuck in the "Starting..." state
mesh still can't reach purokishi.i2p for some reason
mesh ozzz.i2p loads fine. Happy to discover "i2p project should stay politically neutral". It turns out saying racism is bad is not "politically neutral"
mesh dr4wd3: interesting. restarted the i2p router and now purokishi.i2p returns 429 Too Many Requests
mesh but everything works now. I can reach outside sites
dr|z3d great
mesh dr4wd3: not really. It's a very strange error case
dr|z3d if you keep hammering purokishi.i2p in your browser, you'll get that error.
mesh dr4wd3: I mean... something happens that makes outproxies stop working until you restart the router. No idea what it is. But this isn't the first time it's happened to me
dr|z3d you should never have to restart your router. at most, restarting the http proxy tunnel should mostly resolve any issue.
dr|z3d be sure you have "new keys on resume" configured.
dr|z3d and my name's dr|z3d, not dr4wd3. keep hitting that tab button until it completes *correctly*