Cato [MOVED]as if getting nextcloud to run on proxmox wasn't hard enough (you have to modify the .tar.gz archive of the LXD container because some idiot put the filesystem under /rootfs instead of /), now it's running and I wanted to configure it via my reverse proxy. The damn thing always redirects me to its local IP which is obviously not reachable from outside the network! Why is everything so stupid ughhhh
the "official" LXC image from the website that is even suggested to be run in proxmox, after a lot of trial and error, just gives me a HTTP 403. Others also couldn't solve this problem. So now I've switched to using a normal Debian container, installing docker in it and installing the nextcloudpi image in there. Seems to be running, but I cannot get the ports exposed in my local network (wtf?) and when wgetting localhost inside the debian container, I just get improper connections
nextcloud sure is a fucking pain in the ass to install, given how many people use and love it. jesus christ
i used an unofficial proxmox helper script and that seems to have worked
kinda sad but whatever
man nextcloudpi is NOT suited for use with a reverse proxy... i mapped port 4443 to a separate subdomain and it still wants to forward me to port 4443 on that subdomain
i am this close to losing my shit. now i cannot login because none of the usual credentials work???
Why the fuck do I need to run a container for a simple file sync software in the first place? Why do I need an entire VM for my smart home system? Why can't it just be a normal software package that can run alongside other programs? Where the fuck did we go so wrong?
Installing the normal docker image in a container finally worked, then I had to use the reverse proxy for some reason to circumvent a login loop, then modify some permissions... now my desktop client syncs files but tells me for every new file that it can't sync. But it does sync :)))
Kurt🕴️
uvok cheetah 🇩🇪@cato You're right, we should use snap or flatpak instead ;)
@cato But yeah, I get it, I'm especially frustrated with certbot defaulting to snap instructions.
AliveDevil@cato Als alle "Cloud-Native"-Anwendungen haben wollten, und niemand den Hassle haben will sich mit Repositories etc. rumzuschlagen.
"fire `docker run` and forget about it".
Gleiches mit Linux und flatpaks bzw. Canonical "snaps", oder Microsoft mit dem Store/MSIX, und Apple schon lange mit den .app-Ordner Anwendungen.
"fire `docker run` and forget about it".
Gleiches mit Linux und flatpaks bzw. Canonical "snaps", oder Microsoft mit dem Store/MSIX, und Apple schon lange mit den .app-Ordner Anwendungen.
@cato habe auch lieber ein `apt install` oder `dnf install` als ein `(docker|podman) run`, manchmal will ich mich aber nicht um den gesamten Tech Stack kümmen, und dann wird doch docker/podman rausgeholt.
Mastodon läuft hier bspw als Docker-Container, weil ich keine Lust habe, die ganzen Abhängigkeiten richtig zu installieren (Message Queue, Sidekiq, etc.).
Jellyfin hingegen läuft als echte installierte Anwendung, ebenso die Datenbankserver.
Mastodon läuft hier bspw als Docker-Container, weil ich keine Lust habe, die ganzen Abhängigkeiten richtig zu installieren (Message Queue, Sidekiq, etc.).
Jellyfin hingegen läuft als echte installierte Anwendung, ebenso die Datenbankserver.
@cato Nextcloud is far more than a file sync software. If you just need to sync files between devices, I can recommend Syncthing.
@Kurty00 i mostly want a google drive replacement
@cato Then I'm afraid Nextcloud is your best option afaik. My Nextcloud is currently running on Docker, and I remember that I had to do a significant amount of bodging until it ran as it should. Things like mounting stuff to two paths simultaneously, changing random config options and getting the Nextcloud to not try to redirect to localhost or refuse connections from the reverse proxy...
garfieldairlines.net@cato welcome to my job : being a sysadmin
Jakob (Jack/Jackie)@cato And this is why my Nextcloud is running inside an Archlinux container (on Proxmox). Arch has a package for NC in it's repos and it works really well. You just have to be careful to not install PHP and Postgresql major version upgrades without first looking into the NC docs if the new major is supported.
But yeah: NC is one of the more painful-to-maintain pieces of software as a sysadmin... (mastodon is a lot worse though ^^')
But yeah: NC is one of the more painful-to-maintain pieces of software as a sysadmin... (mastodon is a lot worse though ^^')
Izu 🇩🇪🏳️🌈🇳🇱🎈@cato
There are two ways to go around this:
- Invest time, blood and energy into figuring out how things work out (and trial'n'error most of the things)
- Use someone else's struggles to fix your own tech.
- Use one of a million ways to setup software, to then figure out, weeks later, that some configuration options is dangerous, and redoing everything.
Hosting your own stuff is unfortunately - at least not yet - the most straight forward way.
Paul Wunderlich@cato Installing was easy for me compared to updating.
folken@cato here a salt state for nextcloud
nextcloud:
docker_container.running:
- image: 'nextcloud:stable-apache'
- restart_policy: always
- port_bindings: "8080:80"
- binds:
- /var/lib/nextcloud:/var/www/html
- /var/lib/nextcloud/config:/var/www/html/config
- /var/lib/nextcloud/data:/var/www/html/data
- /var/lib/nextcloud/custom_apps:/var/www/html/custom_apps
- /var/lib/nextcloud/apps:/var/www/html/apps
- /var/lib/nextcloud/themes:/var/www
nextcloud:
docker_container.running:
- image: 'nextcloud:stable-apache'
- restart_policy: always
- port_bindings: "8080:80"
- binds:
- /var/lib/nextcloud:/var/www/html
- /var/lib/nextcloud/config:/var/www/html/config
- /var/lib/nextcloud/data:/var/www/html/data
- /var/lib/nextcloud/custom_apps:/var/www/html/custom_apps
- /var/lib/nextcloud/apps:/var/www/html/apps
- /var/lib/nextcloud/themes:/var/www
Skyr@cato hm. Must be a Proxmox/lxc thing. I'm running the Docker containers (automatic updates via Watchtower) with next-to no issues for years now. Ok, user base is small, just for the family, but still...