<superuser> darn
<superuser> is there a way to uninstall a plugin without using the console?
<superuser> I rm'ed the respectivre subdirecotry from .i2p/plugins
<superuser> but that didn't make the problem go away
<superuser> I was trying an old bote version (0.2.6) and it started and bote page loaded, but router console does not load no more. though i think it's ood, given that both are served by same jetty.
<superuser> anyhow, I figured that jetty version change since then, so i decided the oold plugin must be the reason my my console not loading anymore. so i guess, uninstalling it is the way to go
<superuser> hmm, ok. it seems it doesn't like 127.0.0.1 anymore. localhost works
<superuser> and it shows the plugin _is_ gone
<superuser> who knows what I have screwn up
...
<user> 127.0.0.1:7657 back working here after a total router newstart

Am not 100% sure it is bote-caused. but it could be.
well, mine was fine with latest bote and -4 router version.

I updated to -14 and didn't play around much, but it still loaded. At leasat I could acceess clientsconfig and remove the plugin and install an OLD bote version (0.2.6 as opposed to 0.2.9).
then, the console was gone. router was running, i could access eepsites and bote interface, but not standard router console - yes odd.
then rm'd the .i2p/plugins/i2pbote dir as I couldn't uninstall via console (maybe I could have, had I tried localhost instead of 127.0.0.1 before. and I think I did restart and console was still inaccessible.
But finally I rebooted (which means a full router stop and closing firefox etc) and back it was, temporarily. I verified bote was not listed under plugins no more and installed current bote again.

likely not related: for an instant it also warned about being firewalled with inbound tcp enabled, i guess, don't remember exactly as I had hit enter by then and when it reloaded status was back on ok.

If you save the client configuration on /configclients in the console, the console "run at startup" checkbox gets unchecked and you will have no console when you restart. The workaround is to stop I2P, edit ~/.i2p/clients.config and change the line clientApp.0.startOnLoad=false back to true, then start I2P. Working on a fix.

Report #2 from kuri79 may also be related to an incorrect proxy setting in firefox. Don't proxy for 127.0.0.1

The issue where localhost works but 127.0.0.1 does not work may be related to IPv4/v6 OS issues. Not sure.

The issue where it works for a while, then is slow, then doesn't work at all, I have no ideas. The thread dump shows nothing unusual.

on windows it works for me with -15.
linux not yet tested, and possibly caused by an incompatible plugin. i doubt it's purely os-related, because it had been working just fine with that os for years. no update to os made, only router updated and plugin installed. so I'd be surprised if it were os-related.
so as localhost works there and here it's working again too, for me the issue is fixed. dunno about others, tho