Selfhosted

40137 readers

544 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

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Custom Local Domains (sopuli.xyz)

submitted 1 year ago by novarime@sopuli.xyz to c/selfhosted@lemmy.world

40 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

[–] novarime@sopuli.xyz 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.

[–] plo@kbin.social 6 points 1 year ago* (last edited 1 year ago)

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.