IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/10/13
@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+RN_
+dr|z3d
+hk
+orignal
+postman
+wodencafe
Arch
DeltaOreo
FreeRider
FreefallHeavens
Irc2PGuest19353
Irc2PGuest22478
Irc2PGuest48042
Irc2PGuest64530
Irc2PGuest77854
Nausicaa
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
Soni
T3s|4_
Teeed
aargh3
acetone_
anon4
b3t4f4c3
bak83_
boonst
cumlord
dr4wd3
eyedeekay_bnc
hagen_
khb
not_bob_afk
plap
poriori_
profetikla
rapidash
shiver_1
solidx66
tr
u5657
uop23ip
w8rabbit
weko_
x74a6
eyedeekay ReturningNovice, did you get a chance to try either the workaround or the patch from: i2pgit.org/i2p-hackers/i2p.i2p/-/merge_requests/65
ReturningNovice no, do I have to build it?
eyedeekay ReturningNovice no, you should not need anything like that
eyedeekay There are XML files, [base-context.xml, cgi-context.xml, jetty.xml, and jetty-ssl.xml] which potentially contain references to invalid/faulty paths
eyedeekay Those paths will contain this element: `C:/ProgramData/Application Data/` which should be changed to `C:/ProgramData/`
eyedeekay Then the router should be restarted. If the eepsite no longer 404's the fixes worked
ReturningNovice let me take a look
ReturningNovice ok, in jetty.xml it is only in a comment line describing where stuff goes
ReturningNovice this is in /program files/
ReturningNovice this is in /program files/i2p/eepsite
ReturningNovice path not in base-context.xml
ReturningNovice I get the feeling I am looking in the wrong place
ReturningNovice not in cgi-context
ReturningNovice I searched all those files for "program" and it is only mentioned in comments.
ReturningNovice searched instead for C: and that is not in any of those files
ReturningNovice looking in %program data% now
ReturningNovice OK, replaced all occurences in those files in %program data%
ReturningNovice Is checking 127.0.0.1:7658 sufficient? it seems to be working.
ReturningNovice ProgramData\Application Data also found in i2ptunnelconfig.d
ReturningNovice Can't get it to use the privkey properly.
eyedeekay Sorry had to handle something, it's the one in %programdata%
eyedeekay 7658 should be sufficient
ReturningNovice did a bit of side by side comparison and changed a few things to match, but no luck with the dest
ReturningNovice I have an old private key, and an alt eddsa
eyedeekay Shoot, then there's still something pointing to the wrong place I think?
ReturningNovice it is because of ancient signing algo
ReturningNovice 127.0.0.1:7658 is working
ReturningNovice but the newer router won't let me chage from eddsa
ReturningNovice maybe I need to restart the router
eyedeekay Might be, I don't think the xml file changes will apply until you do
ReturningNovice well, still unable to get the sigtype to dsa
ReturningNovice I could use the eddsa key instead... let me try that
ReturningNovice it was missing eepsite/ in front of the key file in the tunnel manager
ReturningNovice you did see I also found that path in annother file?
ReturningNovice yeah, I had restarted for the xml changes... it was my old dsa key that was giving problems because of user typo
eyedeekay Yeah I got it in the scrollback. I'm going to put this log in the issue and go over it all but that should mean we have the issue resolved
ReturningNovice I believe we do.
ReturningNovice thank you!!! U R RockStar
eyedeekay Yeah I think that means all we need to add is the note about i2ptunnel.config.d in the workaround/self-fix
ReturningNovice I'll have a new windows pc to try it in in the next months...
ReturningNovice I'll be more careful importing the eepsite and key to that box
eyedeekay Well hopefully all our config options will line up right too
ReturningNovice the config.d file is created when you first fire up the eepsite server?
eyedeekay Technically it's created on migration
eyedeekay From the old-style i2ptunnel.config to the split-style config
eyedeekay Looks like the path to the keys is a relative path in the default, and on my Linux box it's still relative post-migration, going to remote into the Windows machine and figure out if it's the same
ReturningNovice that was a typo on my part
eyedeekay Oh I see, good then