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?

  • @[email protected]OPEnglish
    2•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

    • @[email protected]English
      0•1 day ago

      But you gotta understand, there’s no subject to your statement. You just said “it doesn’t work” and I have no idea what you’re doing. Are you installing podman? Are you installing caddy? Are you setting up caddy as a reverse proxy? Are you trying to bring your dog back from the dead? I have no frame of reference.

      • @[email protected]OPEnglish
        2•1 day ago

        Sorry for not having expressed what I did. I wrote a podman compose file, pulled the caddy image, wrote a caddyfile, started it and tried to connect to a service via subdomain.domain.tld .

        The caddyfile contains my http and tls ports and the domain and ip for the reverse proxy routing according to the docs.

        The result is no log entry in caddy and no result in the browser or curl.

        • @[email protected]English
          2•1 day ago

          You’ll probably get better help if you post your config and any logs. Caddy may not log an entry to a file but you can watch the console logs to see everything (podman logs caddy or similar.)

          • @[email protected]OPEnglish
            1•1 day ago

            Yes, it works with nginxproxymanager. There’s probably something going on with selinux - I may disable it the next time to test the assumption.

            • @[email protected]English
              1•1 day ago

              Is your caddy container network set to host? Or at least set to a network which is on the same network as your proxied services?

              Ensure that nginx is stopped, and if the domain doesn’t work, attempt to direct connect using your servers IP address and the correct port. If you still can’t connect, check your firewall rules.