Selfhosted

59897 readers

678 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

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

Round Two: Can I manage to set up Jellyfin correctly this time? (lemmy.blahaj.zone)

submitted 10 months ago* (last edited 10 months ago) by compostgoblin@lemmy.blahaj.zone to c/selfhosted@lemmy.world

41 comments fedilink hide all child comments

Hi y’all, thanks for the help with my question yesterday. I did a bit of homework, and I think I’ve got things figured out. Here’s my revised plan:

configure a cron job to update DuckDNS with my IP address every 5 minutes
use ufw to block all incoming traffic, except to ports 80 and 443, to allow incoming traffic to reach Caddy
configure the Caddyfile to direct traffic from my DuckDNS subdomain to Jellyfin’s port

Does this seem right this time? Am I missing anything, or unnecessarily adding steps? Thanks in advance, I’ll get the hang of all this someday!

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

[–] ITGuyLevi@programming.dev 3 points 10 months ago (1 children)

Umm... Not sure if you are serious but knowledge is meant to be shared so... A reverse proxy isn't really for convenience, it sits between two networks and proxies traffic according to specific rules. It also has the benefit of masking the origin server a bit (like its IP) and in a lot of cases can be used as a way to ensure traffic going to a server or service that doesn't support transport encryption actually transverses the internet within a secure tunnel.

[–] littleomid@feddit.org 2 points 10 months ago

Yes, that’s why I said mostly. In this context reverse proxy is being used to access different ports via 80/443 from outside. That is not necessarily the use case you’re mentioning.