Selfhosted

39254 readers

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

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

Custom Local Domains (sopuli.xyz)

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

44 comments fedilink hide all child comments

How do you guys set internal domains?

Say i dont want to type 192.168.1.100:8096 and want a url instead, say jellyfin.servername - how would I go about that? I don't want it exposed online via reverse proxy. I don't need certs. No port forwarding on the router.

How do I type 'jellyfin.servername' into a browser and being up the jellyfin dashboard?

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

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

It's the port that's tripping me. How do I point jellyfin to that domain? It's on docker on port 8096 - the hostname isn't the problem, it's the container.

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

Ah okay. You need some sort of reverse proxy.
I really like caddy. Using it with caddy-docker-proxy in docker-compose makes it quite nifty:

version: '3.7'
services:
  whoami:
    image: containous/whoami
    networks:
      - caddy
    labels:
      caddy: http://whoami.mylab.home
      caddy.reverse_proxy: "{{upstreams 80}}"

networks:
  caddy:
    external: true

Just make sure to explicitly use 'http' instead of 'https'. That way it won't try to create certificates.

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

Cheers. I appear to have something of a mental block with revese proxies. I've used them successfully, but couldn't definitively say I understood them enough to get on with things. I've always had some niche condition on my end that was slightly different to the guide or video I was watching which snafued the process.

I have nginx proxy manager currently up and running and set up wildcards, but no dice on actually mapping anything properly, and there are multiple layers where things can be misconfigured, so diagnosis takes time, which is hard to come by at the moment.

What this post has taught me, is that I need to just spend a weekend playing with reverse proxies enough til they're sunk in. Thanks again for the advice.