Notes »

Tunneling HTTPS service over i2p

Took me a little while to figure this out, and there's probably something I could do to shore things up a bit more, but here's the setup:

I have a HTTPS service on a VPS server and wanted to have it accessible from the i2p network. To do this I used Caddy on the VPS running i2pd.

So, in this example we have 2 seperate VPS servers, both running Caddy, one with the default HTTPS and the other (i2pd server) setup with this Caddyfile (the replace directive requires the replace-response plugin, and I'm still having issues due to redirects I think, also requires the registration of the .i2p short name):

:80 {
	reverse_proxy https://example.com {
		header_up Host {upstream_hostport}
	}
	replace {
		https://example.com:443 http://example.i2p
		https://example.com http://example.i2p
		example.com example.i2p
	}
}

the i2pd tunnels.conf has this entry, more info on i2p tunneling here:

[example]
type = http
host = 127.0.0.1
port = 80
keys = example-key.dat

The example-key.dat is generated automatically by i2pd.

edit SideBar

Page last modified on March 13, 2024, at 03:34 am

^