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.
non_burglar
joined 2 years ago
It's easy to cast this as an all-or-nothing kind of thing, but it is possible to make multilateral deals where everyone involved gets what they want. That's why we want competent and trained people governing these transactions.
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/
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.
... Green snake in a sugar cane field.
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)
Are you OK?
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.
Do you have port 80 to nginx open? Certbot dry run will give you some diagnostics, but that is the most common issue (port 80 being closed).
I also run LE on nginx and afraid DNS.
view more: next ›
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.