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?
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.