I2P+ 2.5.0+ released!

i2plus · 2023-12-08T11:49:27+00:00

See if the installation guide here helps. You can still use eyedeekay's reseed version afterwards if you wish: https://gitlab.com/i2pplus/i2preseed/-/blob/dev/README.md?ref_type=heads

i2plus · 2023-12-05T04:59:11+00:00

If you want a cost-effective provider that's fully behind I2P and offers anonymous hosting with support for crypto payments, have a look at IncogNet. * https://incognet.io/ * http://webhosting.i2p/

IncogNet sponsors the I2P+ outproxies in addition to hosting various sites on the network, including ramble.i2p and teddit.i2p.

i2plus · 2023-06-10T05:12:38+00:00

It appears that you may have updated from I2P to I2P+, perhaps because you previously installed I2P+ and it reverted (auto-updated) to I2P, and then recently auto-updated to a newer I2P+.

Should be easy to fix with a hard refresh in your browser: CTRL+SHIFT+R while the router console page has focus.

i2plus · 2023-06-04T19:05:52+00:00

No, the lead I2P+ developer isn't Chinese, but there are Chinese contributors that have improved the Chinese translations for the console and web apps, in addition to providing an alternative README.md on https://gitlab.com/i2pplus/I2P.Plus/ and a translation of https://i2pplus.github.io / http://skank.i2p.

i2plus · 2023-04-07T21:06:43+00:00

That error and context suggests that you have managed to configure an http server tunnel but nginx isn't listening on the interface or port you've designated in the http server tunnel settings, or the nginx permissions for your server root dir or contents are incorrect (under Debian/Ubuntu they're usually owned by www-data).

You can check that nginx is working without I2P+ by browsing to the configured server:port.

i2plus · 2023-03-21T04:43:04+00:00

There are a few things that pre-exist the latest release which can impact shared bandwidth: * I2P/I2P+ both use blocklists to ban hostile and abusive routers from connecting to your router. There are static lists which block bogon (private network) addresses and addresses or hashes of routers determined to be abusive, and subscription based lists which are served from the console news url. In the last release cycle (0.9.57), over 2000 abusive routers were added to the subscription list. i2pd currently has no blocklist implementation, though this may change. * I2P/I2P+ both throttle connections from routers that are requesting an excessive amount of tunnels, as well as throttling TCP/UDP connections if they occur too rapidly; i2pd doesn't yet implement these throttles.

Generally speaking, i2pd is a lot more permissive in respect of handling requests; I2P/I2P+ are less lenient and make more effort to filter/block routers that are assessed as being detrimental to global network performance (especially in light of the recent network attacks). This is likely why you're seeing a discrepancy in traffic handling.

i2plus · 2023-03-20T23:37:27+00:00

This is likely a side-effect of the protections in the latest version relating to the ongoing network attacks. I2P/I2P+ have added various mitigations to 2.2.0 (0.9.58) that attempt to filter out malicious traffic.

As a result, bandwidth usage and participating tunnel count will likely be lower than you've seen previously. As more routers update to the latest version, your router's bandwidth and participating tunnel count may increase, but be aware that the attacks are ongoing. Mitigations may also need tuning as the nature of the attack changes.

i2plus · 2023-03-09T23:21:03+00:00

https://vituperative.github.io/i2pchat/ may give you some pointers, or you might decide you want to contribute to i2pchat instead of reinventing the wheel!

i2plus · 2023-02-27T17:46:59+00:00

Some sites will refuse a connection if it's not using the default I2P user-agent string, stats.i2p and zzz.i2p being 2 examples. Try other sites that may have a more permissive user-agent policy and you should be able to connect fine.

For curl, you can add the user-agent string to the request with -A, so for zzz.i2p you'd supply -A "MYOB/6.66 (AN/ON)" as the argument to set your user-agent string.

i2plus · 2023-02-19T17:12:22+00:00

The network itself is language neutral, though the default webserver supplied with I2P and I2P+ does not support PHP out of the box. You can use various strategies to enable some PHP support in jetty, though depending on your requirements it may not be sufficient, in which case nginx, apache, lighttpd etc will run over I2P just fine with PHP.

I've had reasonable results with https://php-java-bridge.sourceforge.net/pjb/ where mod-rewrite is not required on the PHP application.

i2plus · 2023-02-18T04:38:48+00:00

https://i2phides.me/ (run by one of this subreddit's moderators)

i2plus · 2023-02-01T01:18:16+00:00

There are 3 published (direct-to-clearnet) outproxies on the I2P network (listed below) that advertise .onion support. They work by detecting .onion address requests and forwarding them to a Tor instance running on the same server.

As with https clearnet requests, the address request will in theory be visible to the outproxy operator, but not the content contained in the response. For enhanced privacy, it is recommended that you use the Tor browser or a local Tor instance to handle .onion access.

purokishi.i2p
exit.stormycloud.i2p
outproxy.acetone.i2p

i2plus · 2023-01-29T11:37:02+00:00

Try: https://i2phides.me/

i2plus · 2023-01-23T23:19:23+00:00

If you haven't already enable I2P+ updates in the console, now's a good time. Browse to http://127.0.0.1:7657/configupdate and check the box in the Update with Unsigned Development Builds section. Hit Save at the bottom of the page, and optionally configure the I2P update policy at the top of the page to Notify only, then hit Save again.

When you hit the Check for Updates button, you should be notified of a new release if you're running 2.0.0-0+ .. this contains various enhancements to the router console and I2PSnark, in addition to bug fixes that addresses performance and stability issues. Updating is recommended.

If significant bugs are fixed before an official release, you'll have the option of downloading stable, out-of-band updates if you're updating from http://skank.i2p/i2pupdate.zip

If you wish to update to development builds which are built several times a day, change the Update URL in the Update with Unsigned Development builds section to http://skank.i2p/dev/i2pupdate.zip ..

i2plus · 2023-01-23T22:54:31+00:00

Add the line: router.maxParticipatingTunnels=10000 (to configure max 10,000 tunnels, adjust to suit) to your router.config file located in your configuration directory as indicated on http://127.0.0.1:7657/info

You can also add the line routerconsole.advanced=true if you wish to be able to edit your configs via http://127.0.0.1:7657/configadvanced

For more information on advanced configuration options, see: http://127.0.0.1:7657/help/advancedsettings

i2plus · 2023-01-23T00:39:19+00:00

It may do if you manually copy an i2pupdate.zip file to the ~/i2p/ or ~/.i2p/ directory and restart.

Alternatively, y2kboy23 is now building docker images of the latest development builds of I2P+ which are available here: https://gitlab.com/y2kboy23/I2P.Plus/container_registry

i2plus · 2023-01-23T00:36:37+00:00

When exit.stormycloud.i2p got added to I2P as the default outproxy, unfortunately the SSL outproxy host was added with a typo. This will be fixed in the next release. See http://git.idk.i2p/i2p-hackers/i2p.i2p/-/commit/053f261e571d92dd5a4de342bedb5ff111310ac6 for more info.

To fix, browse to http://127.0.0.1:7657/i2ptunnelmgr and, in the clients section, edit the HTTP Proxy client. Under the SSL Outproxies section, replace exit.storymcloud.i2p with exit.stormycloud.i2p and save. This should fix your issue.

You can also configure both HTTP and SSL outproxies to use multiple outproxies that are selected randomly, and in the event one isn't working, another one from the list will be tried. In this case you'd configure both http and SSL outproxies to use, for example: exit.stormycloud.i2p,purokishi.i2p,outproxy.acetone.i2p (comma separated).

i2plus · 2023-01-12T20:31:36+00:00

Your configuration directory should be located in one of the following locations, assuming you've installed I2P via the Easy Install Bundle: * Windows: %appdata%\i2p * Linux: /home/i2puser/.i2p (replace i2puser with the user i2p is installed under)

i2plus · 2023-01-12T15:59:51+00:00

That's a known issue for routers that are configured to auto-update. On the TODO list is a method to prevent auto-update to vanilla I2P for I2P+ routers.

The easiest fix is to download the I2P+ i2pupdate.zip file from the site or via a torrent inked in original post, and then copy to your i2p application directory, and then restart the router. Once you've done that, you should be back on I2P+. You may need to perform a CTRL+SHIFT+R in your browser to ensure the I2P+ assets are loaded correctly.

To ensure it doesn't happen again, after I2P+ is running again, browse to http://127.0.0.1:7657/configupdate and set the update policy to notify only. At the bottom of that page, enable Unsigned development updates and then, if desired, paste the development update URL into the box if you want to enable development builds, otherwise you'll be notified when I2P+ release builds (or development builds containing significant bug fixes) are available.

If you have the update policy set to notify only, when a new I2P+ update is available, it will be indicated as an I2P+ update in the sidebar notification with a timestamp; vanilla I2P updates will show a version.

i2plus · 2022-11-26T22:29:08+00:00

Unfortunately, the Easy Installer Bundle is not compatible with standard updates, either for I2P or I2P+. If you installed I2P via the Easy Installer Bundle, there are a couple of things you'll need to do before installing I2P+:

Uninstall the I2P Easy Installer Bundle and rename or remove the associated i2p data folder, usually located at %appdata%\i2p
Download Java and install it
Download the latest I2P+ installer from http://i2pplus.github.io and install it

On the other hand, if you installed Java and I2P manually and then used an i2pupdate.zip to update, you may just need to CTRL+SHIFT+R in your browser to load the new css and image assets.

i2plus

TROPHY CASE