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

Selfhosted

40201 readers
889 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
[–] m12421k@iusearchlinux.fyi 1 points 10 months ago

given that you're looking at vpns I'm assuming you can't do port forwarding on your network. Am I right?

Have you seen zerotier? it lets you create a virtual network. super easy to setup but in the default configuration you're relying on a third party service. not sure if that's ok with you.

The most user-friendly way to do it is hosting it on a https server. for this you need a reverse proxy. checkout caddy. or if you're on docker try traefik.

Most home isps don't let you open port 80 and 443 so you have to use alternative ports which is ok for https but it will make renewing certificates really hard. you have to do it with dns. if it works great. but in my experience it was usually finicky.