Selfhosted

40008 readers

1024 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 posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
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 1 year ago

MODERATORS

[email protected]

[Need Advice] How do I setup remote ssh for my jellyfin server? (lemmy.world)

submitted 1 year ago by [email protected] to c/[email protected]

20 comments fedilink hide all child comments

I currently have a jellyfin server on a rpi4 running raspbian (I think). I'm planning to migrate that to a Dell Wyse mini pc before I go on a month long trip. I would like to be able to ssh into it from outside my home and add movies and stuff. I have already setup ddns for the jellyfin server, so I only need for a way to add movies to it.

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

[–] [email protected] 5 points 1 year ago (3 children)

Do not open port 22 to the work OP. That's horrible advice.

Set up a openvpn server and VPN to your home abc then SSH from inside the network

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (2 children)

Do not open port 22 to the wor[ld]

I often see this parroted but it's not necessarily true. Properly configured and hardened SSH on an up-to-date system is, for all practical purposes, perfectly secure, even if it's facing the Internet.

I still only allow VPN inside my home network, but all my VPSs and dedicated servers (personal and work) have SSH facing the world. VPN is nice to have but not mandatory for this. Hardening SSH servers [1] must be done in all cases, even on "trusted" networks (there is no such thing as a fully trusted network).

[–] [email protected] 2 points 1 year ago (1 children)

Why would you even leave that vector for attack open if you didn't need to?

Seems unnecessary.

[–] [email protected] 2 points 1 year ago

@Lateralking
A VPN is an attack vector, too, and as @vegetaaaaaaa said, it's not like you can slouch on hardening ssh regardless of where it listens.

It also adds complexity. One more thing to go wrong.

Do what you like, of course. Your devices, your choice.
@selfhosted