Selfhosted

59923 readers

510 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

42 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

[–] cyberwolfie@lemmy.ml 3 points 10 months ago

I use Nginx Proxy Manager and whitelist my remote users. They all have static IPs though, so its a workable solution for me.

Before I used a whitelist I would go through the access logs, and could never find any attempts to exploit the endpoints - only some random bots trying to find some admin page assuming it was another service. Not saying you shouldn't take it seriously, but you are likely not subject to these attacks the moment you expose it.

That said, there is a discussion about these endpoints on their repo. At some point they will be fixed (my impression is that they are hampered by legacy Emby code). When they do, you could do this more securely.