can you boot a server if someone tries to connect
can you boot a server if someone tries to connect
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?
You're viewing a single thread.
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
Whats wrong with NPM?
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 }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.
Caddy can do the same and there is a steep learning curve but I switched about a year ago and only need to touch the config file when I add a host. Can even bring that config to a new server and it will stand up once it starts and picks up the config.
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
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.
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.
Thanks again! I managed to set up caddy and it works well so far. Now I am stuck at installing (or using xcaddy. I installed go and the package xcaddy but to me the doc lacks one or two steps. Do you know any tutorial covering that? Thanks!
