@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+T3s|4
+acetone
+dr|z3d
+orignal
+polistern
+postman
+weko
An0nm0n
Arch
FreefallHeavens
Gid
Hikari
Irc2PGuest17080
Irc2PGuest1893
Irc2PGuest4253
Leopold
Minogami
Onn4l7h
Sleepy
Soni
T3s|4_
Teeed
aargh1
admin
anon
b3t4f4c3__
cheddah
eyedeekay_bnc
idk
itsjustme
j6
limak
not_bob_afk
pihole
poriori__
profetikla
qend-irc2p
rapidash
tbqdrn
theglitch
u5657
user101
x74a6h
zer0bitz
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