• 2 Posts
  • 2 Comments
Joined 1Y ago
cake
Cake day: Jul 01, 2023

help-circle
rss

I was really just using SMB for convenience sake, one less protocol for me to turn on and configure. I initially thought about NFS but when I realized how little I know about actually securing NFS I decided against it. Though, I suppose that’s led me to this point here.

Trying it stock is exactly what I was thinking, though what folks have said about NixOS makes me think that’s going to be the first thing I try.

Very first experience was NC-Pi, right before that project got canned. Loved it so much I spent a couple hundred on shared hosting and set v24 up there, but I’ve been trying to move to my homelab because A) One less bill B) I can use the 72TB RAID Array for storage instead of the 30GB storage I paid way too much for.

Honestly have had great experiences with Portainer so far, with Nextcloud being the only real exception. PiHole, Dashy, an introducer for Syncthing, and StashApp all run without a hitch via Compose files dropped into Portainer. Though I am definitely going to take Docker out of the picture for the next NC install which means taking Portainer out as well.


I’ve only ever used the official repositories, basically followed the install documentation to get the letter. I do management of it through Portainer but that’s just a convenience for testing. Once I got the Compose file just right I’d docker up -d inside the folder on the VMs main drive.

The actual files were saved to a mounted SMB share, and I’m not sure if it’s related or not but I also had a media folder mounted as SMB and configured to be shared as External Storage within Nextcloud itself. I keep wondering if the database isn’t killing itself trying to read everything in there…


Moving away from Nextcloud AIO, where do I start setting up a Nextcloud instance WITHOUT Docker?
Hi selfhosted! Hope you're having a good day :) I'm pretty new to self-hosting and have been traipsing through a minefield attempting to make NextCloud AIO work inside Docker. The instance runs for a few days/weeks and then starts getting extremely slow on the website, then dies entirely. Usually, either the ClamAV or Apache containers get stuck in an unhealthy state that no number of reboots or reinstalls can fix. Quick context for how this all works. I have one machine that runs Proxmox and a group of VMs for various purposes. One such VM runs my Nextcloud. This VM is running Ubuntu 23.10, Docker, and the NextCloud AIO package. Another VM hosts OpenMediaVault, which contains a set of SMB Shares mounted to the host VM that act as storage for NextCloud. The symlinks (I think I'm using that word right) on the host VM have user and group permissions updated according to AIO's documentation. Proxmox is configured to boot this VM first, then boot the rest in sequence once the files are available. Right now I've got Nextcloud handling Synchronization of Files, Calendars, Contacts, and Kanban boards via the Deck Extension. Everything else can be abandoned at this point, these are the only functions I'm truly using. If this gives you an idea for an alternative app I'd love to hear it. So after AIO broke for about the 5th time in the 8 months since I started trying to self-host it, I've been looking at alternatives. Before I go that route, I want to try installing Nextcloud without Docker. Some of the posts I've read here suggest that the Docker distribution of NextCloud has serious issues with stability and safely installing updates. I plan to make a new VM entirely for this, Distro undecided. I still want to run it as a VM and still use my SMB shares for bulk storage. So where would I begin if I planned to install NextCloud directly to the VM rather than through Docker?
fedilink

First-time self-hoster here. OS and DNS Questions
Hey /c/selfhosted! Reddit refugee here with a couple questions on things I'm a bit uncertain about. I'll try to keep it brief, but I can clarify anything that needs clarified. I came into a little money recently and I'm coming into some more in the nearish future. My plan is to put some of that into a new server build that I'll use to host VMs running Docker, Portainer, and Nextcloud for starters. Vaultwarden, Jellyfin, Gitea, and some kind of dashboard site will come once I get NextCloud in a good place (I'm torn between Dashy and Heimdall, so if anyone's got opinions I'd love to hear them.) I plan to add more once I'm more comfortable with Docker, and once I have a better idea of how to keep all these things organized and backed up. I have two domains I'm going to use for these, one for test and one for "prod". I use quotes because all of these things are for me only until I'm confident enough to invite my family. I don't plan to make anything that's going to be used by more than a handful of people overall. I've been trying all this with an old server I got off Craigslist which I installed Server 2019 on. I know IIS is a thing, but I'm not certain how or even if IIS plays with Docker, which has me questioning if Windows Server is even worth messing with on the new hardware. Right now, I have a VM set up in Hyper-V which is hosting Docker/Nextcloud in what I'm considering a test environment, but it's not accessible outside the home. Mostly I did this to learn Hyper-V for work, so I'm not married to Windows Server or even Windows for all this. The other problem, of course, is DNS. It does appear that my ISP has given me a static address (or at least they haven't changed it since I moved in 6 months ago). Assuming that's true, I'm not certain how I'd go about configuring a DNS server at home and making it accessible outside my home. If anyone's got any resources they want to recommend for setting up a DNS server in-home for this kind of thing, I would love to see them. tl;dr 1. Is there any advantage to using Windows Server to host VS some flavor of Linux or even Windows Pro, or am I just wasting my time (assume cost is not a factor) 2. Am I making my life harder trying to manage DNS through Windows Server, and is there an alternative if so. Linux alternatives also accepted
fedilink