Page 1 of 1
ROUTER CONSOLE
Posted: 30 Jun 2018 23:48
by jukeboxer07
Why is accessing the router console taking too much time. I have waited for half an hour then gave up
.
Am accessing it through
http://localhost:7657/
It just keeps on connecting...
Re: ROUTER CONSOLE
Posted: 01 Jul 2018 07:15
by slumlord
I have seen this before on a router that had run out of memory. You can try restarting your router as well as trying to reach it on
http://127.0.0.1:7657/
To restart your router, find the directory that I2P is installed in (e.g.
~/i2p is the default on a
.jar install) and run:
Re: ROUTER CONSOLE
Posted: 01 Jul 2018 10:20
by jukeboxer07
slumlord wrote: ↑01 Jul 2018 07:15
I have seen this before on a router that had run out of memory. You can try restarting your router as well as trying to reach it on
http://127.0.0.1:7657/
To restart your router, find the directory that I2P is installed in (e.g.
~/i2p is the default on a
.jar install) and run:
Still no change
Re: ROUTER CONSOLE
Posted: 01 Jul 2018 11:12
by echelon
Hi
Which system?
What does the wrapper.log tells you?
It maybe a issue with libjetty9 and only java 8 installed on debian. Try running java 9 and jetty9.
echelon
Re: ROUTER CONSOLE
Posted: 01 Jul 2018 15:34
by jukeboxer07
echelon wrote: ↑01 Jul 2018 11:12
Hi
Which system?
What does the wrapper.log tells you?
It maybe a issue with libjetty9 and only java 8 installed on debian. Try running java 9 and jetty9.
echelon
Thanks, this was helpful. It is all well now.
I was using java 8 before.