infra-cookbook/misc/i2paddr.txt

10 lines
1.8 KiB
Plaintext

`i2pport port_number` starting from 11000 until nothing is printed and it exits with code 1. we're up to 11040 but check just in case (`i2pport 11040` for example)
`create_i2p service_name keyfile_name clearnet_domain port [type] [host] [inport]` service_name is the name of the service (e.g. libreddit, gitea).
keyfile_name is the name of the file that the keys are stored in; it will be put in /var/lib/i2p/vern.[INPUT].dat (replace [INPUT] with keyfile_name). typically this is the same as the service_name, unless the inport is different, in which case it is to be "www" (unless it needs to be the same address as something else, for example yc.vern.cc and YaCy Server use the same "yacy" keyfile).
clearnet_domain is only used as the title of the service, so put the clearnet domain (e.g. lr.vern.cc, git.vern.cc), or if there's a different inport, just input the name of whatever the service is, properly capitalized (e.g. SSH, Gemini, YaCy Server).
port is the port you chose above, e.g. 11040. two services may not have the same port.
type is optional, only needed if it isn't an http tunnel, it will be "server" for generic TCP tunnels (most non-http), and "udpserver" for UDP tunnels (mumble and minetest use this).
host is the address to listen on, will usually be 127.0.0.1 if the service is on the tildeserver (most of the time), or 10.7.0.1 if it's located on the VPS (among-sus used to be). inport is the port to listen on. by default it's 80, meaning web services won't need this option. but for non-http services (e.g. SSH, Gemini) it is required to be inputted (e.g. 22, 1965).
Nginx will listen on the `port` value, not the `inport` value, so make the `listen` directive must have the same port as the `port` you used earlier. (you get it).
Address helper is http://whatever.vern.i2p/?i2paddresshelper=$(i2pb64 whatever)