Closed Shoalsteed closed 1 year ago
/console is a welcome page that provides information about error messages, warmings and troubleshooting information.
**this text is updated for the router console NOT the site Welcome to the I2P Network**
The first time your I2P router makes connections to the network, it may take a few minutes to integrate your router into the network. As it begins to make this connection by finding peers, you will see the number of Active Peers begin to grow in the sidebar Peers status section. When your router is ready, you'll also see a Local Tunnel named Shared Clients listed there, and possibly other clients and servers. These Local Tunnels provide connections to the I2P network, enabling your bittorrent, email, web proxy and other services. Your Network Database indicates all known peers on the network. Additionally, you can monitor existing Peer Connections, and view existing Tunnels and their status. More information is available on the help page.
When the I2P router starts up, and during normal operation, the tunnel build readiness indicator in the sidebar may indicate that I2P is "Rejecting Tunnels." This is normal behaviour.
I2P Software Overview Simply copy this page: https://geti2p.net/en/about/software
Add: I2P in Private Browsing link
Error Messages and Warnings
Reseed: In some cases there are issues with finding Peers and connecting with the I2P network. If the router is encountering this issue, it will provide the option to "Reseed" in the sidebar. Clicking the Reseed button will fetch a bundle of Peers router infos.
While I2P will work fine behind most firewalls, your speeds and network integration will generally improve if the I2P port is forwarded for both UDP and TCP. If you think you have opened up your firewall and I2P still thinks you are firewalled, remember that you may have multiple firewalls, for example both software packages and external hardware routers. If there is an error, the logs may also help diagnose the problem.
OK: Your UDP port does not appear to be firewalled.
Firewalled: Your UDP port appears to be firewalled. As the firewall detection methods are not 100% reliable, this may occasionally be displayed in error. However, if it appears consistently, you should check whether both your external and internal firewalls are open for your port. I2P will work fine when firewalled, there is no reason for concern. When firewalled, the router uses "introducers" to relay inbound connections. However, you will get more participating traffic and help the network if you open your firewall. If you think you have already done so, remember that you may have both a hardware and a software firewall, or be behind an additional, institutional firewall you cannot control. Also, some routers cannot correctly forward both TCP and UDP on a single port, or may have other limitations or bugs that prevent them from passing traffic through to I2P.
Testing: The router is currently testing whether your UDP port is firewalled.
Hidden: The router is not configured to publish its address, therefore it does not expect incoming connections. Hidden mode is automatically enabled for added protection in certain countries. Too see the countries that are on this list refer to the Strict Countries List.
Firewalled and Fast: You have configured I2P to share more than 128KBps of bandwidth, but you are firewalled. While I2P will work fine in this configuration, if you really have over 128KBps of bandwidth to share, it will be much more helpful to the network if you open your firewall.
Firewalled and Floodfill: You have configured I2P to be a floodfill router, but you are firewalled. For best participation as a floodfill router, you should open your firewall.
Firewalled with Inbound TCP Enabled: You have configured inbound TCP, however your UDP port is firewalled, and therefore it is likely that your TCP port is firewalled as well. If your TCP port is firewalled with inbound TCP enabled, routers will not be able to contact you via TCP, which will hurt the network. Please open your firewall or disable inbound TCP above.
Firewalled with UDP Disabled: You have configured inbound TCP, however you have disabled UDP. You appear to be firewalled on TCP, therefore your router cannot accept inbound connections. Please open your firewall or enable UDP.
Clock Skew: Your system's clock is skewed, which will make it difficult to participate in the network. Correct your clock setting if this error persists.
Private TCP Address: You must never advertise an unroutable IP address such as 127.0.0.1 or 192.168.1.1 as your external address. Correct the address or disable inbound TCP on the Network Configuration page.
SymmetricNAT: I2P detected that you are firewalled by a Symmetric NAT. I2P does not work well behind this type of firewall. You will probably not be able to accept inbound connections, which will limit your participation in the network.
UDP Port In Use - Set i2np.udp.internalPort=xxxx in advanced config and restart: I2P was unable to bind to the configured port noted on the advanced network configuration page . Check to see if another program is using the configured port. If so, stop that program or configure I2P to use a different port. This may be a transient error, if the other program is no longer using the port. However, a restart is always required after this error.
UDP Disabled and Inbound TCP host/port not set: You have not configured inbound TCP with an address and port on the Network Configuration page, however you have disabled UDP. Therefore your router cannot accept inbound connections. Please configure a TCP host and port on the Network Configuration page or enable UDP.
Client Manager I2CP Error - check logs: This is usually due to a port 7654 conflict. Check the logs to verify. Do you have another I2P instance running? Stop the conflicting program and restart I2P.
Troubleshooting
Check Your Configuration and Bandwidth Allocation I2P functions best when you can accurately reflect the speed of your network connection in the bandwidth configuration section. By default I2P is configured with some fairly conservative values that will not suit many use cases, so please take time to review these settings and correct where necessary. The more bandwidth you allocate, specifically upstream bandwidth, the more you will benefit from the network.
Check Your Proxy Settings If you cannot see any websites at all (not even i2p-projekt.i2p), make sure your browser's proxy is set to access http traffic (not https, not socks) via 127.0.0.1 port 4444. If you need some help, there's a guide to configuring your browser for I2P use.
Check Your Logs Logs may be helpful to resolve a problem. You may wish to paste excerpts in our forum for help, or perhaps paste it instead and reference the link on IRC for help.
Verify Java is Up to Date Ensure your Java is up to date. Check your Java version at the top of the logs page.
Problems running on Legacy Hardware
[Linux/BSD] If you can't start the router with i2p/i2prouter start try the runplain.sh script in the same directory. Root privileges are never required to run I2P.
The I2P Software (I2P)
When you download the I2P software, a set up wizard will guide you through a few configuration steps while your router is making its first connections to the network. This happens the same way that your home router connects you to the Internet. During the set up process, you will be given the option to test your bandwidth and set your bandwidth limits in order to ensure a good connection as a network peer.
The I2P software is what allows you to connect to the I2P network. It also includes an admin panel (router console) where you can access a handful of applications, monitor your network connection, as well as other helpful options for setting up your own connection preferences.
Applications are made available through a webUI, which listens at 127.0.0.1:7657.
Applications.
The I2P Router Console: Here is where you can see your network connections and information about your router. You will be able to see how many peers you have, and other information that will help if you need to troubleshoot. You can stop and start the router as well. You will see the applications that the software includes, as well as links to some community forums and sites on the I2P network. You will receive news when there is a a new software release, and will be able to download the latest version here as well. Additionally, you can find shortcuts to other available applications. The console is customizable and includes a default light theme with a dark theme option.
SusiMail: SusiMail is a secure email client. It is primarily intended for use within the I2P network . It is designed to avoid leaking information about email use to other networks. SusiMail is bridged so it can send and receive email from the internet as well. Occasionally you may see some services like Gmail classifying it as spam, which you can correct in your Internet email service providers settings.
I2PSnark: Snark is an I2P network only BitTorrent client. It never makes a connection to a peer over any other network.
The Address Book: This is a locally-defined list of human-readable addresses ( ie: i2p-projekt.i2p) and corresponding I2P addresses.(udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p) It integrates with other applications to allow you to use those human-readable addresses in place of those I2P addresses. It is more similar to a hosts file or a contact list than a network database or a DNS service. There is no recognized global namespace, you decide what any given .i2p domain maps to in the end.
The QR Code Generator: Besides the Address Book, I2P addresses can be shared by converting them into QR codes and scanning them with a camera. This is especially useful for Android devices.
I2P Hidden Services Manager This is a general-purpose adapter for forwarding services ( ie SSH ) into I2P and proxying client requests to and from I2P. It provides a variety of “Tunnel Types” which are able to do advance filtering of traffic before it reaches I2P.
Static Site Template: A template that you can modify to set up your own self-hosted I2P site is included.
See additions https://github.com/Shoalsteed/UX/issues/53
This would be an extended version of this https://geti2p.net/en/about/software
/home
This is the landing page of the I2P router console. It is comprised of a sidebar, news, and quick links to I2P applications, a selection of I2P sites, services, help and configuration.
Sidebar The sidebar will display: -what version of I2P you are running -how long it has been running -your router connection status -tunnel build status -alerts when a new version of I2P is available for download -reseed if required -options to stop, restart your router
News The news section will display highlights from a new release, and alerts when there is a need to do an update to any plugins, or extensions or the I2P router software itself. This section can be displayed or hidden based on your preference.
Applications The I2P router includes : I2P Addressbook , Email, Hidden Services Manager, Torrents, and a Web Server. This section provides links to each.
I2P Community Sites This is a collection of sites and services that the I2P team hosts, with exception of the Tin Hat. They are are all internal to the I2P network. They include links to zzz' dev forum, the community forum, the project Gitlab, and more. If you want to check if your browser is configured properly and if you are connected to the I2P network, click on one of these options to find out!
Configuration and Help In this section you can access your bandwidth sharing options, help and FAQ , and add plugins to your router, or customize the look of your router console as part of the configuration options available.
Network and Developer Information Links in this section include access to I2P technical docs, the project Bugtracker, Trac Wiki, and metrics options for people who are interested in I2P network statistics. Logs for your router can be accessed here as well.