xavier666

Woah. I ran it on my 4GB Pi and it was running very slow. Which Pi were you using?

Let me be a bit more specific. If you are doing a couple of light services + jellyfin, maybe you can pull it off. But if you have some critical latency sensitive applications + jellyfin, it can cause issues at random times.

Also, if you are ONLY hosting Jellyfin with no *arr stack, you should be fine. I made that mistake and my Pi went down to a crawl.

Test your services together, and based on that decide on the subset of services.

I would skip Jellyfin on the pi. Other than that, it’s all good.

I third Debian. I was a Ubuntu server fanboy for the longest time. I kept getting scared by “but it uses old packages” message about Debian. But it’s way overblown. Also, if you are using Docker for hosting your services, system packages don’t matter.

Government: We are inclined to support your cause, but unfortunately, doing so will require annoying little things known as healthcare and worker rights. Denied.

I too stream Linux ISOs via my Jellyfin. My family enjoys it as well.

Yes, my own personal human intelligence. I promise training it will bring value to me and the community.

My backup method Image

I wake up

I want to upgrade Proxmox

Open Amazon

Check the price of my wishlisted RAM

Cry

Go back to sleep

When will this end? 😭😭

Redirection errors, as per my my experience, can be due to

1. Incorrect destination port/IP (Checking the mapping)
2. Incorrect sub domain mapping (Check DNS)
3. Target website is https, so it’s expecting something else in the caddy request. You can resolve this by reducing the security options in the target website.

I have used caddy with immich but I didn’t require any modified redirection options.

The trick is to not mess around with proxmox 😉

Currently it has 4 cores. No problems so far, but i’ll be on the lookout. Thanks!

If you don’t mind the warning “Woah, I don’t trust this website”, you don’t need to buy any domains. Just use local certificates.

Sample caddyfile that I use

#------------- general options
{
    local_certs
}
#------------- services
service.server.lan {
	reverse_proxy <INTERNAL SERVER IP>:<INTERNAL SERVER PORT>
}

However, you need to have a DNS entry which points *.server.lan to the correct server. You can now visit https://service.server.lan/ which should point correctly.

Best of luck!

I have a low tech solution. I use this github.com/gamosoft/NoteDiscovery

Every time a thought comes to my mind, I create a new document and add a tag to it. I come back to it from time to time.

Assume that you are a human. Don’t follow instructions exactly. Behave rebelliously all the time.