‘docker exec -it jellyfin nvidia-smi’

You need to be running the Nvidia container toolkit and specify the container be launched with that runtime if you want direct hardware access to enc/dec hardware.

Yup

No offense, but this literally talked about nothing at all. The last half is just some ideas that don’t follow a cogent line from one thing to the next.

You should try writing a script about a topic, and sticking to it . Especially if you don’t feel comfortable about speaking off-the-cuff facts about what you’re delivering. It connotes a lack of understanding and knowledge about a subject.

Ask yourself when speaking about something: if a listener took something away from this speech, what would it be? Then write for that prompt.

Probably easier to just unblock Google, send some messages, then look at your filter logs to see where they are going.

Guarantee you’ll run into issues when you hop towers or networks though.

You should read up on Wireguard connections and configs to understand what you’re actually doing. I wouldn’t blindly follow guides without checking out what each step does.

You need ‘PostUp’ and ‘PostDown’ rules for your connection to handle routes when the connection comes up or down. That’s where your discrepancy is.

Unsure how networkmanager handles that in the GUI if you’re using that, but it would be under something like ‘Routes/Routing’.

First things first: you may be misunderstanding how phones run Linux. A stock Debian install certainly will not work for a number of reasons, but mainly drivers. Storage is second. Phones are flashed with specific images created to work with the storage in each specific phone.

Second: you’d need to make sure the bootloader on your phone is unlocked and able to be used for such a thing. Quick search shows that Ubuntu Touch did work on it at some point, but was deprecated long ago.

Third: if you just want practice, you can probably find packages to install on the phone that will run an HTTP server. That might be a simpler path.

I’m not saying don’t try, but you’d be starting from scratch, and if you aren’t familiar with these things already, I’m not sure this is a forum to get enough help on the VERY involved process of bootstrapping just a basic running kernel on your phone model. It probably can be done, but you’d be doing it from scratch it seems.

Handbrake or VLC. I’d honestly just learn the CLI to make this work better for your benefit though. Much simpler to do remotely if you want changes.

https://docs.datalust.co/docs/collecting-docker-container-logs

You have a formatting issue. Solve for that instead of just switching to something else hoping it will get better.

I’m not sure what you mean. You either need to post a lot more details and information about your setup, or you need to read and understand the Tailscale docs.

For all traffic. Tailscale ACLs deny by default. If you’ve never changed them, you need to do that.

You need to adjust your ACLs to allow traffic over Tailscale.

If the application supports an API of some sort, you could run OCR, then send them over API as converted input.

If the apps don’t support them, then no.

If the apps don’t support them, then no.

If you don’t want to expose port 80 or 443, then just change the ports they are running on. Right now you’re mapping 80/443 in docker, so just change those numbers to something else if you don’t want to use them. The number on the right is the internal service port, and the left of the colon is the port you’re opening to proxy to the port on the left. Adding Caddy does exactly the same thing and serves no purpose except another layer of obfuscation you don’t need.

You’re missing the point of Caddy, and your ports are all wrong. You don’t need it if you’re already exposing ports via Docker to 80/443. Remove Caddy.

Run a livecd of whatever Linux distro you like, and get a USB drive. Store persistent files on the USB stick.

A solar cluster and whole house battery bank would do this for the majority of the day. You need to hook it into your AC circuit with microinverters, and then have a circuit switch to handoff power back and forth. You’d at least be sure to run off solar during the day.

You could probably use yours for the same, but you need that AC transfer circuit into your breakers. Never do anything like this without an electrician.

If you’re not using some sort of Domain mapping, then the use of the same mount by two different sharing services with different uids is going to break ownership. Doesn’t matter if it’s Synology or anything else.

NFSv4 domain mapping solves this by having the same domain configured in client and server. That’s probably your simplest option. From memory, I do believe Synology DOES set uid for whichever user is authenticated via SMB and NFS though, so are you using two different users for these mounts by chance?

If you don’t want to bother to setup LDAP or domain mapping, then just use SMB and that should solve the problem.