I’ve got a mini pc which is running always and another one which consumes a lot more power for e.g. jellyfin.

Can I configure it such that the jellyfin server only boots if I connect to it? E.g. I try to connect to jellyfin.y.com and then the server boots because the mini pc tries to connect to it.

I already figured out how to let it sleep automatically as soon as nobody is watching.

Edit: can I add the magic package to the reverse proxy?

    • enemenemu@lemm.eeOPEnglish
      1·
      2 days ago

      Thanks! I use wake on lan with rtcwake to boot at a certain time. I also found an app via which I can boot the server via wake on lan. But it would be nice if it could wake up just by requesting the service

  • Mubelotix@jlai.luEnglish
    1·
    2 days ago

    I made a tool that can hibernate systemd services when no request get through their associated nginx service. Using it on jellyfin, works great

    • enemenemu@lemm.eeOPEnglish
      0·
      2 days ago

      Thanks!

      I use nginxproxymanager, I’ll try to find something similar (I couldn’t find something directly)

        • enemenemu@lemm.eeOPEnglish
          0·
          2 days ago

          I’d be happy to switch if I had a good tutorial for caddy. Unfortunately I couldn’t find one.

            • enemenemu@lemm.eeOPEnglish
              0·
              2 days ago

              It doesn’t work. I can’t manage to debug it.

              Fedora server. Podman. Selinux. Port 8443. Ipv4.

              • Xanza@lemm.eeEnglish
                0·
                1 day ago

                it doesn’t work

                …what exactly doesn’t work. You’re not really giving me enough to help you with.

                • enemenemu@lemm.eeOPEnglish
                  0·
                  1 day ago

                  Thx for offering your help.

                  If I would know, I could debug it, but I don’t know where the problem is. I assume the problem is somewhere with podman or selinux

          • Xanza@lemm.eeEnglish
            1·
            2 days ago

            I mean, use what you want. But caddy is significantly easier to configure. It additionally handles SSL and protects your proxy targets with zero configuration (by default) and supports live configuration reload via the admin interface. It’s tits.

            Here’s my config: http://i.xno.dev/u/fc8N0n.png

            Caddy is running a wildcard SSL cert, so once I’ve connected my box to cloudflare, I can setup a subdomain by simply adding it to my caddy config. No additional setup is required. It also works directly with docker, so if you install the lemmy (name of the container) docker container, you can reverse_proxy by simply (assuming they’re on the same docker network):

            lemmy.domain.com {
    reverse_proxy lemmy:80
}
            • themachine@lemmy.worldEnglish
              1·
              2 days ago

              That sounds more or less to be exactly what I’m doing with NPM currently. I don’t see how it’s easier to configure as all I did was fire up the NPM container, log in, and add my host targets.

              NPM also handles SSL both standard http verification as well as DNS auth for wildcards.