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...
ROUTER CONSOLE
- jukeboxer07
- Posts: 3
- Joined: 30 Jun 2018 23:40
Re: ROUTER CONSOLE
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:
To restart your router, find the directory that I2P is installed in (e.g. ~/i2p is the default on a .jar install) and run:
Code: Select all
./i2prouter restart
- jukeboxer07
- Posts: 3
- Joined: 30 Jun 2018 23:40
Re: ROUTER CONSOLE
Still no changeslumlord 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:
Code: Select all
./i2prouter restart
Re: ROUTER CONSOLE
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
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
- jukeboxer07
- Posts: 3
- Joined: 30 Jun 2018 23:40