zzz
eyedeekay, to work on websocket issues, would you please update git.idk.i2p router to trunk? I doubt I accidentally fixed it already but just in case
zzz
eyedeekay, the su3 script I mentioned the other day is in zzz/su3-launcher project
zzz
on websocket, right now I see that the CONNECT works, and then over that socket it does GET ws://git.idk.i2p/-/cable and that comes back 404 not found, and then the browser closes the socket
zzz
that's all I can see on this side
zzz
actually, anybody running services, if you can update to -16-rc that would be great, the more testing the better
zzz
eyedeekay, https i2pgit.org is serving a selfsigned localhost cert from 2013???
zzz
nevermind, my snafu
zzz
ok on clearnet the request is for GET wss://i2pgit.org/-/cable (note wss vs. ws) and also comes back 404
zzz
does commenting on tickets work on clearnet?
zzz
yes but it's very slow
eyedeekay
The fuck? Ok I did something wrong trying to fix the runners, I'll be right on it
eyedeekay
Probably something with the reverse proxy
eyedeekay
Just got back from pickup at the airport will be here til it's fixed
eyedeekay
ah it's the 'snakeoil' cert, that's why it's so old...
eyedeekay
I'll put git.idk.i2p on trunk ASAP, I have to do a deb dev build and those take a little while
eyedeekay
I only got half these messages on my phone back at my desk putting the info together
zzz
no the cert was my issue not yours
zzz
sorry for false report
eyedeekay
Thanks yeah I got that after I put all the messages in order
eyedeekay
But I'll still do the deb dev build from trunk on my launchpad and get it on i2pgit.org
zzz
great, put it on allo your things
zzz
for me websockets aren't working on clearnet either, are they for you? go to any single issue, then do inspect->network
eyedeekay
Yeah I see them breaking too I think it's between nginx and gitlab
eyedeekay
I have an idea
eyedeekay
Need a little while to edit configs
zzz
on clearnet the POST when adding a comment works but takes a lonnnng time. over i2p, it times out after about 33 seconds, I'm trying to figure out why, because the timeout is configured for 60 sec
eyedeekay
I'm trying to cut down on some of the trickery required to get it to work with multiple hostnames, gitlab expects to be configured on exactly one hostname and all the internal parts reflect that, so it has to listen on localhost only then nginx has to rewrite everything incoming and outgoing with the correct hostname or localhost depending in where it's going
eyedeekay
There's so much careful tweaking in this config file it's borderline intractable, so I'm reorganizing the whole thing
eyedeekay
Because at this point which thing breaks depends on which tweak I un-do
eyedeekay
All of this also ties into how it handles TLS and CORS
eyedeekay
and maybe half a dozen other possible things
eyedeekay
I'm not going to be convinced of any one source of issues until I get that under control
eyedeekay
Like if you configure it to listen on localhost http only then it expects ws not wss but if you upgrade it with nginx then clearnet ws breaks, but if you configure it to listen on https only then I2P ws breaks
eyedeekay
I *think* what I have to do is listen on localhost with gitlab, then add the self-signed certificated to the trusted certificates, then configure nginx to proxy the localhost interface instead with essentially all the same rewriting intact
eyedeekay
But that also means that git.idk.i2p will have to go https
eyedeekay
That's fine though
eyedeekay
self-signed obviously, I don't think I can abuse the Let's Encrypt certificate
RN
If you want to test the dev version but don't want to build it youreself you can grab an updater file at I2Peek-a-Boo.i2p/i2pupdates.html 2.3.0-16-rc
RN
If you want to test the dev version but don't want to build it youreself you can grab an updater file at I2Peek-a-Boo.i2p/i2pupdates.html 2.3.0-16-rc
RN
oops. sorry for repeat