this post was submitted on 26 Dec 2025
30 points (96.9% liked)

Selfhosted

53977 readers
408 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
30
What could be causing HTTP Error: 403 when trying to connect to my I2P site that's hosted using nginx? (infosec.pub)
submitted 2 days ago* (last edited 2 days ago) by graysonuniverse@sh.itjust.works to c/selfhosted@lemmy.world
8 comments fedilink hide all child comments
 

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;
	}
}
top 8 comments
sorted by: hot top controversial new old
[–] 7toed@midwest.social 1 points 9 hours ago

Did you try what your error message suggests? Also didn't know ybat nginx could do i2p, unless thats new or you're using some extension

[–] slazer2au@lemmy.world 23 points 2 days ago (1 children)

Not to sound snarky but did you follow the instruction in the error message?

[–] graysonuniverse@sh.itjust.works 2 points 2 days ago

Where is the 'advanced configuration'?

[–] WhyJiffie@sh.itjust.works 16 points 2 days ago (1 children)

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

[–] graysonuniverse@sh.itjust.works 9 points 2 days ago

Thank you so much. This explained it clearly and your fix worked.

[–] princess@lemmy.blahaj.zone 6 points 2 days 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

[–] LodeMike@lemmy.today -1 points 2 days ago (1 children)

The answer is literally in your screenshot.

[–] WhyJiffie@sh.itjust.works 5 points 2 days ago* (last edited 2 days ago)

I think that's misleading. I doubt OP wants to access the router console with this name.