@eyedeekay
&zzz
+R4SAS
+RN_
+Stormycloud
+cumlord
+dr|z3d
+hagen
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch
BubbRubb
Daddy
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest13210
Irc2PGuest20240
Irc2PGuest21940
Irc2PGuest32330
Irc2PGuest74254
Irc2PGuest76033
Irc2PGuest78101
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
SlippyJoe_
T3s|4__
Teeed
Uncrushed_
aargh2
ac9f_
acetone_
anontor2
b3t4f4c3___
dr4wd3
duanin2
erniee
eyedeekay_bnc
fus3r1
leopold
makoto
n1
nilbog-
not_bob_afk
onon_1
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66_
thetia
u5657
uop23ip
vivid_reader56
w8rabbit
wodencafe2
x74a6
zelgomer
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