Selfhosted

61475 readers

891 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

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
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.
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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

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;
	}
}

you are viewing a single comment's thread
view the rest of the comments

[–] 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.