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?
If you have a reverse proxy running on the mini pc and handling jellyfin.y.com then there is this plugin which will send the WoL packet to the jellyfin server when a request is sent.
Thanks!
I use nginxproxymanager, I’ll try to find something similar (I couldn’t find something directly)
I use nginxproxymanager
I’d be happy to switch if I had a good tutorial for caddy. Unfortunately I couldn’t find one.
How complex is your nginx reverse proxy? Caddy is relatively straight forward: https://i.xno.dev/u/fc8N0n.png
It doesn’t work. I can’t manage to debug it.
Fedora server. Podman. Selinux. Port 8443. Ipv4.
it doesn’t work
…what exactly doesn’t work. You’re not really giving me enough to help you with.
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
I believe so—see Wake-on-LAN.
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
That’s how it works. Wake-on-LAN wakes the computer if the computer receives a network request. Which is the same thing you’re asking for, right?
Also an option, systemd based, could be to use systemd socket files, which (as far as I understand) opens a dummy socket and starts the matching service as soon as it’s requested.
I love systemd.
Is this what you suggest? https://cybso.de/blog/2017-02/how-wake-lan-remote-host-demand-using-systemds-sockets/
This sounds like a proxy that sends a magic packet if it can’t reach the service. That sounds great
Basically yeah, though other solutions may be easier or more integrated. Using systemd sockets is especially useful if you want to start a service on the local server that is always on, with a service that uses a lot of resources in the background without other user interaction
I think you’ll want to look into Wake On LAN to do this. I can’t give you instructions (tried once unsuccessfully on a Windows installation) but that should be enough to get you started.
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
I made a tool that can hibernate systemd services when no request get through their associated nginx service. Using it on jellyfin, works great