Migrating From I2P Eepsite to Tor Hidden Service

I2P eepsites use the I2P router as a proxy, routing HTTP to the .i2p address. Tor hidden services are configured directly in torrc with HiddenServiceDir and HiddenServicePort. The application server (Nginx, Apache, application daemon) listening configuration changes from I2P's SAM/BOB bridge to a direct local socket or localhost port bound to Tor's HiddenServicePort. Database connection strings, configuration files referencing the I2P address, and any internal links need updating to reference the new .onion address. If the application generates absolute URLs internally, update BASE_URL or equivalent configuration variable to the new .onion address.

Add to /etc/tor/torrc: HiddenServiceDir /var/lib/tor/myservice/ and HiddenServicePort 80 127.0.0.1:8080. Restart Tor: systemctl restart tor. Read the generated .onion address: cat /var/lib/tor/myservice/hostname. Configure Nginx or your application server to listen on 127.0.0.1:8080. Test access using Tor Browser with the generated .onion address. Compare application behavior between the I2P and Tor deployments: ensure database queries, authentication flows, file uploads, and other functionality work correctly in the new Tor context.

Maintain the I2P eepsite in parallel with the new Tor hidden service during the transition period. Post a prominent notice on the I2P site directing users to the new .onion address. Publish the new address through existing communication channels used by your community (forum posts, email lists, Telegram channels). Maintain the I2P service for 30-90 days after publishing the Tor address to allow community members to complete transition. Monitor traffic on both services to verify the community is successfully migrating. Decommission I2P only after traffic has substantially shifted to the Tor service.

I2P's user community is smaller and more technically sophisticated than Tor's. I2P users are more familiar with privacy tools and expect certain norms. Tor's user community is larger and more diverse. When migrating from I2P to Tor, be prepared for a different user base with potentially different engagement patterns, support needs, and expectations. Content appropriate for the I2P community may need to be presented differently for the broader Tor audience. This is especially relevant for technical documentation (I2P users need less explanation), community rules (may need clearer articulation for newcomers), and trust establishment (I2P community trust relationships do not transfer automatically to the Tor context).

Clear migration communication prevents user loss during the transition. Prepare a migration announcement that includes: the new .onion address, a clear explanation of why migration is happening, the timeline for maintaining the I2P service, and how to verify the announcement is authentic (sign it with a PGP key published before the announcement). Distribute through multiple channels: the I2P site itself, any community social channels, and direct contact with known community members. Create a redirect or landing page at the I2P address that prominently displays the new .onion URL. Establish the Tor service's identity with a fresh PGP key published at the .onion address, allowing community members to verify future communications.