@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
eyedeekay
Also runners are back
orignal
is there a chance for zzz.i2p back?
eyedeekay
Not up to me
orignal
ofc this question is not to you
Opicaak
eyedeekay, git.idk.i2p returns 502, https returns invalid length, SSL_ERROR_RX_RECORD_TOO_LONG.
dr|z3d
now required.
Opicaak
https returns invalid length, SSL_ERROR_RX_RECORD_TOO_LONG.
dr|z3d
check back soon, he'll have it fixed. it's probably in progress.
dr|z3d
in the meantime, github.
zzz
eyedeekay, see RN's port81 doc for how to do this correctly
eyedeekay
The post says '2 days' I tried to give some warning
eyedeekay
But yes I will thanks zzz
eyedeekay
Opicaak use https on Wednesday
eyedeekay
502 will be fixed in a sec
eyedeekay
Tried to forward the same port as the signal proxy and container stalled
zzz
503 Service Unavailable This I2P website is not configured for SSL.
zzz
nice error message but we serve it over http so it's useless
zzz
I guess we could spin up a cert if that happens
orignal
who uses https in i2p?
zzz
one more person soon
orignal
the only reason for https is an outproxy
eyedeekay
WebSockets, WebRTC, couple dozen other bits of obscura in all major browsers...
zzz
i think I can fix the error message, let me try
zzz
not so easy, not for this release