&zzz
+FreefallHeavens
+RN_
+Romster
+acetone
+eche|off
+mareki2p
+nilbog
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+wodencafe
Arch
Danny
Irc2PGuest15434
Irc2PGuest16019
Irc2PGuest20377
Irc2PGuest33925
Irc2PGuest35412
Irc2PGuest48148
Irc2PGuest77921
MatrixBot
NiceBoat
Onn4l7h
Onn4|7h
Over
R4SAS
Sisyphus
T3s|4
Teeed
aargh4
ahiru
ananas
anontor2
b3t4f4c3__
cims
dr4wd3_
duanin2
ice_juice
mahlay
makoto
marek
n2
noidea
not_bob_afk2
o3d3
poriori
profetikla
r00tobo
rapidash
rednode
sahil
solidx66
stormycloud[m]
sublimia
test7363673
uop23ip
urist_
vivid_reader56
x74a6
zelgomer
eyedeekay
new dev build is up: github.com/i2p/i2p.i2p/releases/tag/i2p-2.4.03 tag is slightly wrong I'll fix that on the next one
eyedeekay
zzz when you get a chance, could you try to login to clearnet gitlab under a fresh firefox profile, something like:
eyedeekay
mkdir tmp-profile && firefox --profile ./tmp-profile
eyedeekay
should do it
eyedeekay
I know clearnet gitlab is breaking with I2PIPB(I2PIPB users should just use git.idk.i2p instead) right now but it looks like everything else should work
eyedeekay
including the git.idk.i2p side, but both sides work much better with HTTPS
zzz
i did that and logged in but what is that supposed to fix?
eyedeekay
I thought you were unable to log in?
zzz
on the i2p side
zzz
422
zzz
clearnet is my workaround
eyedeekay
Can you try that with a fresh profile too?
zzz
i guess but have to set the proxy
eyedeekay
Usually it will honor env variables if it sees them, auto-configure by prefixing http_proxy and https_proxy
zzz
git.idk.i2p redirects to git.idk.i2p/users/sign_in
eyedeekay
Yes https is now required to log in, it's the only way to fix the websockets
zzz
didnt get that memo
zzz
https is timing out, no response. http responds immediately
zzz
but could be a bug on my side, I'm running keepalive patches
zzz
can somebody else try it?
eyedeekay
It worked the first time from my phone, https sites seem to time out instead of showing an unreachable error
eyedeekay
But I can see it from at least 2 devices
zzz
I'll have to investigate issues on my side then
zzz
in the meantime, still getting 422 for http login on the i2p side
eyedeekay
I'll nuke the redirect but expect issues with the http anything with gitlab
zzz
well if http doesn't work then keep the redirect or tell people it won't work
zzz
ok, signed in successfully with https over i2p using another router. investigating further
R4SAS
eyedeekay: have you updated git instance? heard about CVE?
R4SAS
s/git/gitlab