A workaround that I decided to go with was to simply extend my backup of the nextcloud snap to simply include the entirety of /var/snap/nextcloud instead of just taking the data directory, and the dump of the database. If I restore /var/snap/nextcloud, everything is immediately restored to its previous working order. This seems to accomplish what I want.
I still have no idea what was causing the previous issue, though. I’m thinking that it might be that some important files, or directories are being left out in the previous backup that nextcloud is expecting to be present, but I’m really not sure.
Original Post
I have been scratching my head for hours over this – I’m really not sure what the problem could be. I have nextcloud installed as a Snap on Ubuntu Server.
Here’s how I went about restoring the backup (fresh install of nextcloud):
Copy over the data: # rsync -Aax data-backup data-directory
Drop the existing database: # nextcloud.mysql-client -e "DROP DATABASE nextcloud"
Create a new database: # nextcloud.mysql-client -e "CREATE DATABASE nextcloud"
Restore the dumped database: # nextcloud.mysql-client nextcloud < database-dump
When I log in to nextcloud in the browser, it initially appears that it worked fine: calendar data, task data, contacts, etc. are all properly loaded, and the images viewer is displaying images; however, when you look at the files tab, there’s nothing there, and, when you try to create a folder, it spits out an error saying “Unable to create folder”. If I run nextcloud.occ files:scan --all it can see all the files in the data directory just fine, it’s just not able to display them in the files taband I cannot figure out why. I would really appreciate any help, ideas, or suggestions.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Check also all parent directories, as the whole path need to have access (execute) permissions.
Tried this. Still nothing.