I mean, you just keep asking different people whether a thing that does X exists. They’ve all said no, but you can use Y plus mods to do it. Doesn’t seem good enough for you.

Now you’ve risen to “VLC cant do that”. I’ve shown you it can, and you not only beak back at me about it being CLI, but downvote me as well. Thanks for that.

streaming not transcoding

Literally the first sentence:

“This functionality allows you to link VLC’s transcoding capability with a segmenter which will in turn create the series of files needed for http live streaming to the iPhone”

You don’t know what you’re talking about, and you don’t understand your own problem.

Regardless of any info you get here, you will still need to problem-solve. Good luck.

Come on, dude. Now you’re just trolling.

https://wiki.videolan.org/Documentation%3AStreaming_HowTo/Streaming_for_the_iPhone

Quit while you’re ahead and just go do some reading.

Oof, a lot of vitriol in this thread.

In the end, security is less about tooling and config, and more about understanding the risks and acting accordingly.

I expose jellyfin to the internet, but only to a specific public IP. That reduced my risk considerably.

There are a number of ways to install nextcloud, and docker is only one of those.

Yes, NC isn’t ideal in many ways, but it shouldn’t be as painful as you’re describing to run it.

Paperless-ngx is great, but it is particularly bad at handling PDF documents. Roughly half my documents just won’t import.

https://github.com/paperless-ngx/paperless-ngx/issues/3933

https://www.reddit.com/r/selfhosted/comments/yfjxww/paperlessngx_not_all_pdf_files_can_be_imported/

https://github.com/paperless-ngx/paperless-ngx/issues/2187

Turnkey images are usually built on popsicle sticks and chewing gum; they use old packages, their configs are often really janky and they do not like being updated.

I’m not kidding you, you’d be better off building nextcloud in a generic debian container.

As for the errors, as others have mentioned these are more or less easily fixed one at a time.

There’s a bunch of posts about the iptables-save function of the built-in iptables module not working in many cases, so I figured it was a safer bet to suggest the playbook include an actual command invocation.

In my personal experience, the module doesnt actually save the persistent rule in about half the cases. I haven’t looked into it much, but it seems happen more on systems where systemd iptables-firewall is present. (Not trying to start a flame war)

Generally, you set up a rule + command playbook, where the command invokes the iptables-save command.

I read the old thread and now this one.

As I understand it, you want to create connection between clients on your lan, but you don’t trust your lan, so it’s like having a raspberry pi server and some client both on the coffee shop network and you want them to communicate securely?

Tailscale is what you want. Easy setup, free, and allows exactly this to happen.

I was looking for this. Op seems to be obsessed with “zero trust”, so creating a trusted area for this stuff would be an easy win.

Kind of a vague question, but I take it you mean OS-level hardening, which should be fine with CIS hardening.

In a virtualized environment, there are many security layers to take care of: network access, storage, api control, identity access, cluster config, backups, etc.

Don’t be flippant.

This is like going to a car enthusiast forum and asking “any potential problems with driving a car that may or may not be stolen?”

You have indicated that you’re aware of the potential repercussions of running a personal project in a publicly-funded environment.You’ve already been told that this is unethical everywhere and illegal in many places.

If you are so sure of your indemnity because it’s “your device”, why are you asking on Lemmy?

It can manage KVM, so I don’t see why not .

Side question, but where are you hearing this about incus?

I’m wrapping up 9 years of using proxmox and I have very specific reasons for switching to incus, but I this is the third time I’m fielding questions in the last month about incus.

I think so.

It is LXD + KVM, so way more and finer tune control on lxc instances. It can run OCI images as well, so for docker instances with only a few configs and no persistent storage, it is actually quite handy. For docker instances that need pretty complicated compose files, I just run docker inside an lxc for now, until I figure that out.

Bash variable manipulation is really, really fun.

More incus:

• mounting persistent storage into containers (cheating by exporting NFS from my proxmox zfs into the incus host.
• wrote a pruning backup script for containers, runs daily, keeps last 7 days and the first of the month
• passed through hardware (quicksync) into jellyfin container (it works!)
• launched an OCI container (docker home assistant) natively in incus (this is a game-changer!)

Next:

• build 2nd incus node
• move all containers from proxmox to incus
• decom proxmox
• setup Debian with NFS export

I use eleventy. Similar to other static site generators.

Because NAT acts as a firewall with a “default deny” policy for incoming packets, but no other rules. You cannot prevent a device on the private subnet side of a NAT from attempting to communicate with an “outside” ip with nat alone, nat doesnt understand the concepts of accept/deny/drop.

All nat does is rewrite address headers.

The machines behind a NAT box are not directly addressable because they have private IP addresses. Machines out on the general Internet cannot send IP packets to them directly. Instead, any packets will be sent to the address of the NAT box, and the NAT box looks at its records to see which outgoing packet an incoming packet is in reply to, to decide which internal address the packet should be forwarded to. If the packet is not in reply to an outgoing packet, there’s no matching record, and the NAT box discards the packet.

It’s a confused topic because for a lot of people, nat does essentially everything they want. As soon as you get into more complex networking where a routing table needs to be updated, or bidirectional fw rules, it becomes apparent why routing + fw + nat is the most common combo.