Nothing wrong with Boost Mobile, or any other discount telecom provider either. It’s not like the phone signals taste different lmao

It’s just a hallmark of “I bought the cheapest domain name TLD available”.

That’s not necessarily bad if all you need is something to get the job done, but there is a stereotype associated with it.

I think it is generally okay to bundle the root domain certificate and the wildcard for its subdomains into a single renewal.

So for example:

example.com
*.example.com

The data is all stored server-side. The worst that could happen is the sync connection stops working and you need to redownload the files. Nothing gets deleted by these commands. They will still be on your disk and accessible by you.

If this breaks Nextcloud, it indicates something’s wrong with your installation.

I’m guessing you’re talking about the client, right? The data folder on the server shouldn’t be touched or modified, except by Nextcloud.

Check who owns the folder. I’ll assume the folder is at ~/Nextcloud, but if it’s not, just substitute in the path to the Nextcloud folder.

You can check who owns the folder using ls:

ls -la ~/Nextcloud

This should give you something like:

drwx------ 10 user group    4096 2024-03-04 00:00 Nextcloud

Where the word “user” is in the above example should be the name of the owner of the directory. Where the word “group” is should be the group.

If either is root, check to make sure the Nextcloud client is not running as root (using sudo or otherwise).

Otherwise, give yourself ownership of the directory:

sudo chown username:username -R ~/Nextcloud

Replace username with your username.

Mine is… eh. It’s alright. I don’t use any of the apps. Just the actual sync functionality. Sometimes when I’m moving files around there’s a problem where the entire thing just stops responding. My MediaWiki instance still works, just not Nextcloud. Not sure why this happens and not sure if it also happens to other people.

For comparison, it is running on a Contabo VPS M