this post was submitted on 26 Dec 2025
35 points (97.3% liked)

Selfhosted

61475 readers
385 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
35
What could be causing HTTP Error: 403 when trying to connect to my I2P site that's hosted using nginx? (lemmy.nz)
submitted 7 months ago* (last edited 7 months ago) by graysonuniverse@sh.itjust.works to c/selfhosted@lemmy.world
9 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 9 comments
sorted by: hot top controversial new old
[–] slazer2au@lemmy.world 25 points 7 months ago (1 children)

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

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

Where is the 'advanced configuration'?

[–] WhyJiffie@sh.itjust.works 16 points 7 months 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 7 months ago

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

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

[–] Madiator2011@piefed.social 2 points 7 months ago

Right now it looks like you trying to expose your i2p console via i2p I would not do it. If you need remote access I would use tailscale this is how I have my setup.

[–] 7toed@midwest.social 1 points 7 months 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

[–] LodeMike@lemmy.today -1 points 7 months ago (1 children)

The answer is literally in your screenshot.

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

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