Selfhosted

61475 readers

851 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

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