My setup exists of one local server that basically hosts Jellyfin and an arr stack. I only access this server locally with PC, TV and phone, however I might setup a Wireguard based remote access in the future.

Should I use a reverse proxy like Caddy so I can access the different containers with a local domain name like jellyfin.myserver.local?

I am also interested in hosting Adguard home but how can this work together with Caddy, won’t they both conflict as a DNS server?

I appreciate any possible advice on these topics.

Thank you.

  • MajinBlayze@lemmy.worldEnglish
    141·
    5 months ago

    Don’t use jellyfin.server.local

    .local is reserved for mdns, which doesn’t support more than one dot. (Though it may still sometimes work).

    In any case, to make that work you need either a DNS server on your network or something like duckdns (which supports wildcard entries).

    • Lem453English
      8·
      5 months ago

      For people wanting the a very versatile setup, follow this video:

      https://youtu.be/liV3c9m_OX8

      Apps that are accessed outside the network (jellyfin) are jellyfin.domain.com

      Apps that are internal only (vaultwarden) or via wireguard as extra security: Vaultwarden.local.domain.com

      Add on Authentik to get single sign on. Apps like sonarr that don’t have good security can be put behind a proxy auth and also only accessed locally or over wireguard.

      Apps that have oAuth integration (seafile etc) get single sign on as well at Seafile.domain.com (make this external so you can do share links with others, same for immich etc).

      With this setup you will be super versatile and can expand to any apps you could every want in the future.