~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
+FreefallHeavens
+Xeha
+bak83_
+cumlord
+hk
+profetikla
+uop23ip
Arch
Danny
DeltaOreo
FreeRider
Irc2PGuest19353
Irc2PGuest48042
Irc2PGuest64530
Irc2PGuest98199
Meow
Nausicaa
Onn4l7h
Onn4|7h
Over
T3s|4
acetone_
anon4
anu3
boonst
enoxa
mareki2pb
mittwerk
not_bob_afk
plap
poriori_
shiver_
simprelay
solidx66
u5657
weko_
T3s|4
dr|z3d: after restarting the latest, iirc it was dated 20 Sep ~02:30 UTC my console tires to loads endlessly - and then eventually times out. 127.0.0.1:7657/sitemap /home /configupdate are all impacted - so I am flying blind. Same behavior on both laptops
T3s|4
*tries to load
dr|z3d
sorry to hear that, T3s|4, new update in the pipes, hopefully will fix :|
dr|z3d
all else fails, T3s|4, revert to skank.i2p/i2pupdate.zip until things become a little less choppy. postman is reporting some serious connection issues with the latest build with the latest upstream patches.
T3s|4_
np and gotcha dr|z3d :)
dr|z3d
that said, you might just need a hard refresh if you're not able to load the console, or a clear cache.
T3s|4_
dr|z3d: hard refreshes had no impact, nor did clearing FF's cache for 127.0.0.1. Now proudly running 14+ but at least the console works. Please let me know when a new update is ready :)
dr|z3d
will do, T3s|4
dr|z3d
ok T3s|4, new build up.
T3s|4
dr|z3d: Thanks for your heads-up, but nope, the latest just replicates the endless router console loading problem I reported earlier. I've again reverted to 14+
T3s|4
RN: do you have a way to test the latest + build without risking data? Perhaps a VM, or similar
dr|z3d
T3s|4: strange. you don't have an old config lurking in router.config do you? routerconsole.oldHomepage=true or similar?
T3s|4
no dr|z3d - nothing similar on either laptop
dr|z3d
ok, and what browser, T3s|4?
T3s|4
FF
dr|z3d
ok, fine.
dr|z3d
and the behavior is a constant retry and then fail to get to /home ?
dr|z3d
what else? password protected console?
dr|z3d
ok, I think I can reproduce the issue here. it's specific to accessing the console via
T3s|4
yep, no /home or /sitemap et al with either of the two latest, but as I said 14+ works as expected. I've never used a password protected console
dr|z3d
yeah, it's .. we have a workaround for the time being..
dr|z3d
routerconsole.redirectToHTTPS=false in router.config and then access the site via :7657 not :7667
dr|z3d
site/console
dr|z3d
If I look at my browser dev console, it looks like is sending a large stream of data instead of the page. I cancelled at around 2MB, which for the homepage isn't right, so I'll dig into it. thanks for bringing the issue to my attention.
T3s|4
dr|z3d: I do remember FF sometimes saying a request was something like 'too large', most just timed out without explanation
dr|z3d
yeah, what looks like timing out is probably just an attempt to see the page over https, I'll try and identify what I've fat fingered.
T3s|4
dr|z3d: routerconsole.redirectToHTTPS=false embedded and saved. Restarted into the latest, and yet 127.0.0.1:7657/home and 127.0.0.1:7657/sitemap, among others will not load
dr|z3d
can you try a different url like /jobs and make sure you ctrl+shift+r while doing so, if necessary repeatedly, T3s|4?
T3s|4
same with any console page; /jobs tries to endlessly load, and a hard refresh appears to have no impact on its 'static' state
T3s|4
restarting FF also has no impact
dr|z3d
and you're definitely on http not https?
dr|z3d
:7657
dr|z3d
> routerconsole.redirectToHTTPS=false in router.config and then access the site via :7657 not :7667
T3s|4
not sure what more I can do than type: 127.0.0.1:7657/jobs
dr|z3d
what's the browser url displaying? :7667 or :7657 ?
T3s|4
as in 127.0.0.1:7657/sitemap
dr|z3d
ok, so you've modified the redirect to https config. testing a fix here, let's see...
T3s|4
do you mean the non-statement of routerconsole.redirectToHTTPS=false actually defaults to =true ?
RN
oi T3s|4, I do test in a vm, but it is currently running Canon dev build. Would spin up another but for lack of disk space.
dr|z3d
T3s|4: yeah, by default we redirect to https in the console.
dr|z3d
I don't see the issue on only which is why I recommended that config.