snex
zero downtime migration status: complete
not_bob
That should have worked.
not_bob
There we go.
not_bob
Talk about lag.
not_bob
snex: Nice
snex
huh. one of my eepsites is publishing an incorrect leaseset
snex
actually
snex
might be my addressbook
dr|z3d
if the private key is correct, everything else should be.
dr|z3d
that is, assuming the private key is the same one associated with a hostname when you registered it.
dr|z3d
check the private key for the server is correct, ie the one you migrated and renamed.
dr|z3d
if it isn't, you'll have a default i2ptunnelkey.dat file instead.
dr|z3d
easily fixed, if it is the case. just point the tunnel at the correct .dat file and restart it.
snex
when i hit the b32 listed by the tunnels page it works for both. its only the addressbook entries that done
snex
dont*
snex
so like, if i enter total nonsense into the privkeys field, it seems to accept that. doesnt seem to be a good way to tell if it is erroring or not
snex
got it. i think it saw a folder in the config and created that folder as well as new keys since i was assuming the wrong base dir
dr|z3d
if you have a hostname in the server tunnel config, you'll see an add to addressbook icon on the index page. easiest way.
dr|z3d
as for the addressbook, if the add to addressbook submission doesn't work, the data should remain in the form, otherwise it worked.
dr|z3d
make sure you're not prefixing the b32 with or just use the b64 address. you can toggle the display of that on the main index page with the + icon on the global control panel.
snex
i just had to assume the correct base-dir for the key file
dr|z3d
the base dir is ~/.i2p/
snex
thats what i was assuming. but it wasnt
dr|z3d
well I don't know how you've managed to futz your config dir, that's quite an achievement of itself.
snex
yeah. im a pro at stuff like that