Self Hosted - Self-hosting your services.

506 readers

1 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

No harassment
crossposts from c/Open Source & c/docker & related may be allowed, depending on context
Video Promoting is allowed if is within the topic.
No spamming.
Stay friendly.
Follow the lemmy.ml instance rules.
Tag your post. (Read under)

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.

Cross-posting

!everything_git@lemmy.ml is allowed!
!docker@lemmy.ml is allowed!
!portainer@lemmy.ml is allowed!
!fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
!selfhosted@lemmy.ml is allowed!

If you see a rule-breaker please DM the mods!

founded 3 years ago

MODERATORS

Zoe8338@lemmy.ml

dogmuffins@lemmy.ml

testman@lemmy.ml

Lemmy; how do you do?? (self.selfhost)

submitted 1 year ago by paulie420 to c/selfhost@lemmy.ml

18 comments fedilink hide all child comments

I've been working with the two suggested LemmyNet installation methods; Docker and Ansible. Neither are too wild of a setup, but they aren't plug and play docker-compose-like, either.

I want to run a LemmyNet on a subdomain; lemmy.domain.com, and use nginx-proxy-manager to point traffic in the right direction, but it will be on the same local IP... some port changes will need to be made.

Is anyone running their own instances? Have suggestions or tips with things that helped you lean up a lemmy.subnet?

Cheers!!

pAULIE42o
. . . . . . . . . . .
/s

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

[–] wizjenkins@lemmy.wizjenkins.com 1 points 1 year ago (1 children)

I host my instance exactly like this with Nginx Proxy Manager. Here's my config:

Block Common Exploits and Websockets Support - on
Add a custom location with the following settings:
- proxy_set_header X-Real-IP $remote_addr;
- proxy_set_header X-Forwarded-For $remote_addr;
- proxy_set_header X-Forwarded-Host $remote_addr;
- real_ip_header X-Real-IP;
- real_ip_recursive on;
for SSL turn on HTTP/2 Support

I had to add the custom config so that I would get the IP address of the clients and federated servers. Otherwise I was hitting rate limits on the Lemmy server.

[–] paulie420 1 points 1 year ago

Ahh; these settings are interesting... I turned on 'block common exploits', but HTTP/2 support might be smart, too... yer custom location stuff is above my head, but you've got me sniffing a bit now. :P