this post was submitted on 22 Dec 2023
35 points (100.0% liked)

Selfhosted

39964 readers
248 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

My self-hosting experience is primarily with Plex and qBittorrent, but I'm trying to get a digital library set up that will be available remotely. I've been reading about some options, but I'm not sure about what is best to use or how to deploy it.

What is the best way to make Kavita available to remote users safely from a home server?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 10 months ago (1 children)

Why wouldn’t the funnel solution be exactly what I’m looking for? Feels almost too good to be true.

If I’m understanding this correctly, I just have to set up Tailscale funnel on my local server, and it will generate a publicly accessible IP through their proxy that can be accessed remotely in a similar fashion to how Plex premium routes signals through their proxy for easy remote access? If that’s correct, that’s basically my dream solution because it only exposes kavita and doesn’t require a secondary server to bounce the signal through.

[–] [email protected] 1 points 10 months ago* (last edited 10 months ago) (1 children)

There's three reasons:

  • As mentioned in the blog post, Funnel is still a rather new feature. It's still in beta.
  • It goes far beyond Tailscale's core purpose; it's basically a separate service.
  • It's free for now but probably won't be for long. TS' core functionality will likely be free or at worst very low cost for a long time but public hosting is a helluvalot more costly and also dangerous.

That said, if I had to share something with the public internet temporarily, I'd try not doing that first but could see myself using TS Tunnels.

[–] [email protected] 1 points 10 months ago (1 children)

I need to share permanently though. Would it be better to use tailscale to make a connection to a remote server and then use that server as a front end that bounces back to my home server?

[–] [email protected] 1 points 10 months ago* (last edited 10 months ago)

Not really. As soon as you have a path from global internet into your home network, all bets are off and you're now in charge of securing all of that against the entire world.

That said, if this is a regular old HTTP service, I believe Cloudflare Tunnels offer a way to put an authentication mechanism in front. This can work if, just like with Tailscale, you have a limited known set of users but the difference is that those users don't to have to install and use a VPN client to access your service but rather authenticate using an "external" HTTP service through their browser. Again, I do not believe this works for services accessed through APIs and certainly not ones using custom protocols.

I can't stress enough that getting those remote users to use Tailscale is probably the best and easiest solution.