The nginx server block is listening on a port other than 80, if that matters. It’s all my VPN provider will allow me to forward.

server {
	listen [PORT];
	server_name mysite.i2p;

	location / {
		proxy_pass http://127.0.0.1:7657/;
		proxy_set_header Host $host;
		proxy_set_header X-Real-IP $remote_addr;
		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
	}
}
  • WhyJiffie@sh.itjust.worksEnglish
    16·
    1 day ago

    port 7657 is to the router console, do you really want that? if no, you need to check the tunnel manager for the port configured for your eepsite. its in the I2P Hidden Services list. the default entry uses port 7658

    if you followed the advice of others to change the advanced config, you should probably revert this change because you don’t need it.

    btw sometimes it may be useful to also expose the router console. but since that’s only for you, you don’t want others using it, configure an encrypted leaseset for it, which makes the router console’s eepsite invisible to others on the network. you should keep the router console’s authentication when you do this. https://geti2p.net/en/blog/post/2021/09/07/Level-Up-Encrypted-Leasesets

  • 𝓹𝓻𝓲𝓷𝓬𝓮𝓼𝓼@lemmy.blahaj.zoneEnglish
    4·
    1 day ago

    that error is coming from I2P, not nginx

    so good news? your nginx configuration is probably fine

    bad news? I know fuck all about I2P. assuming you’re intending to reach the “router console”, you could probably follow the suggested configuration change in the error message to Do That Thing