Install Nextcloud 13.0.0 on Fedora 27
-
@nashbrydges said in Install Nextcloud 13.0.0 on Fedora 27:
I have a Nextcloud instance running on Hyper-V using a 500GB dynamically expanding disk that is working perfectly. I can see that it's barely using any of the space. I followed these instructions for creating a Nextcloud instance on Fedora and when I use a dynamically expanding disk, for some reason, the install does not recognize it as a full 500GB disk so after uploading a few large test files, I'm out of space at around 10GB. The Nextcloud instance is on a Fedora 27 minimal install.
Any ideas where I may have gone wrong? I used this command to create the disk:
New-VHD -Path C:\MyVHDs\nextcloud.vhdx -SizeBytes 500GB -Dynamic -BlockSizeBytes 1MBDoes Fedora not play well with dynamically expanding disks? I could instead create a fixed disk but I'd like to avoid that if I can.
Haven't tried that, but I would not expect it to like that.
-
@scottalanmiller said in Install Nextcloud 13.0.0 on Fedora 27:
Haven't tried that, but I would not expect it to like that.
So you're suggesting I'd stick to fixed disk instead? Curious as to why Ubuntu seems ok with it but Fedora isn't.
-
@nashbrydges said in Install Nextcloud 13.0.0 on Fedora 27:
@scottalanmiller said in Install Nextcloud 13.0.0 on Fedora 27:
Haven't tried that, but I would not expect it to like that.
So you're suggesting I'd stick to fixed disk instead? Curious as to why Ubuntu seems ok with it but Fedora isn't.
Requires a hook. I'm sure that there is a way to do it.
-
@nashbrydges said in Install Nextcloud 13.0.0 on Fedora 27:
I have a Nextcloud instance running on Hyper-V using a 500GB dynamically expanding disk that is working perfectly. I can see that it's barely using any of the space. I followed these instructions for creating a Nextcloud instance on Fedora and when I use a dynamically expanding disk, for some reason, the install does not recognize it as a full 500GB disk so after uploading a few large test files, I'm out of space at around 10GB. The Nextcloud instance is on a Fedora 27 minimal install.
Any ideas where I may have gone wrong? I used this command to create the disk:
New-VHD -Path C:\MyVHDs\nextcloud.vhdx -SizeBytes 500GB -Dynamic -BlockSizeBytes 1MBDoes Fedora not play well with dynamically expanding disks? I could instead create a fixed disk but I'd like to avoid that if I can.
Last time I check, the default Fedora Server install will only partition enough for its need. But leave the rest untouched.
-
@black3dynamite said in Install Nextcloud 13.0.0 on Fedora 27:
Last time I check, the default Fedora Server install will only partition enough for its need. But leave the rest untouched.
Looks like you might be right. Cockpit only shows the root and boot mounts for a total of 16GB.
-
I used Cockpit to expand the root folder to the max allowable which recognized the 500GB disk. Now shows correctly:
Logged back into Nextcloud and I've now got access to the expanded storage. Sweet!
-
@nashbrydges I had the same issue on a Fedora install. I created a 3Tb dynamic disk and had to manually partition Fedora to get the full disk for /. This was Hyper-V 2016.
-
@brandon220 said in Install Nextcloud 13.0.0 on Fedora 27:
@nashbrydges I had the same issue on a Fedora install. I created a 3Tb dynamic disk and had to manually partition Fedora to get the full disk for /. This was Hyper-V 2016.
This is a normal Fedora tactic. I'll make a guide on this later or something.
-
@brandon220 Using Cockpit was ridiculously easy,
-
@jaredbusch Good to know. This was my first time using Fedora.
-
I have a 2 Tb Nextcloud install on Ubuntu (16.04) from a couple years ago. I need to migrate everything to a new server using Fedora but a migration seems harder than it should be. Hopefully I will tackle it soon. I've not had any issues with Ubuntu but everyone here seems to dislike it.
-
The default behaviour of a Fedora Server install is to just use what's needed. During install, you need to select the "custom" option and add space to your
/partition and/or add a/homeif you desire.See the first section of my post here: https://mangolassi.it/topic/16084/installing-fedora-27-lamp-stack-plus-wordpress
-
@brandon220 said in Install Nextcloud 13.0.0 on Fedora 27:
I have a 2 Tb Nextcloud install on Ubuntu (16.04) from a couple years ago. I need to migrate everything to a new server using Fedora but a migration seems harder than it should be. Hopefully I will tackle it soon. I've not had any issues with Ubuntu but everyone here seems to dislike it.
"Dislike" is strong. "Don't like compared to common alternatives" is better.
-
Whats the best way to configure the data directory? Do I create a large VM or a separate disk mounted on the data folder?
-
@mattbagan said in Install Nextcloud 13.0.0 on Fedora 27:
Whats the best way to configure the data directory? Do I create a large VM or a separate disk mounted on the data folder?
For a file server, I'd have a separate .VHDX for the file storage, and mount it as /DATA
-
@mattbagan said in Install Nextcloud 13.0.0 on Fedora 27:
Whats the best way to configure the data directory? Do I create a large VM or a separate disk mounted on the data folder?
Varies on your needs. NextCloud recommends separate BtrFS volume. I like a separate LVM2 volume with XFS.
-
@scottalanmiller @Tim_G Thanks for the info. I will have a separate disk for the data. I will be using this guide to migrate from ubuntu to fedora.
-
Very nice! I've done this before on Fedora 23 with OwnCloud, but the procedure was confusing.
I wanted to add something for users who might have an issue like I did. I have a separate physical disk I wanted to setup for the data disk, but found myself running through most of your procedure without having setup or mounted the disk. I took your advice and used the default /var/www/html/nextcloud/data path.
At the NextCloud wizard, I received a "can't read or write into the data directory" message. I knew it had something to do with permissions. First, I had to re-issue the chown apache:apache -R /var/www/html/nextcloud command because once the disk was mounted the data folder reverted back to root:root - that's a given. But the same error came up. So, I figured it was SELINUX and I re-ran the selinux_config.sh script, which gave me an error for each folder saying it was already defined. Even so, I tried NextCloud again and had the same data directory error.
A little poking around and I found this out: you have 2 commands in SELINUX: "semanage fcontext" and "restorecon" ...
The "already defined" error was coming from the semanage fcontext command, so I read a bit about restorecon and discovered that if you add an "-F" parameter, it will force the command rather than bypass it if it's already been run. There is no error from restorecon, it just silently doesn't work. Adding the -F parameter worked: restorecon -R -F ${ocpath}/data.Thank you, I have a nicely running NextCloud system now!
-
@sopdahl said in Install Nextcloud 13.0.0 on Fedora 27:
Very nice! I've done this before on Fedora 23 with OwnCloud, but the procedure was confusing.
I wanted to add something for users who might have an issue like I did. I have a separate physical disk I wanted to setup for the data disk, but found myself running through most of your procedure without having setup or mounted the disk. I took your advice and used the default /var/www/html/nextcloud/data path.
At the NextCloud wizard, I received a "can't read or write into the data directory" message. I knew it had something to do with permissions. First, I had to re-issue the chown apache:apache -R /var/www/html/nextcloud command because once the disk was mounted the data folder reverted back to root:root - that's a given. But the same error came up. So, I figured it was SELINUX and I re-ran the selinux_config.sh script, which gave me an error for each folder saying it was already defined. Even so, I tried NextCloud again and had the same data directory error.
A little poking around and I found this out: you have 2 commands in SELINUX: "semanage fcontext" and "restorecon" ...
The "already defined" error was coming from the semanage fcontext command, so I read a bit about restorecon and discovered that if you add an "-F" parameter, it will force the command rather than bypass it if it's already been run. There is no error from restorecon, it just silently doesn't work. Adding the -F parameter worked: restorecon -R -F ${ocpath}/data.Thank you, I have a nicely running NextCloud system now!
No problem. I am happy you figured it out.
I did not think about the -F paramter to force it to redo it. That is a good idea to add to the instructions in case someone redoes something like you did.
-
The one additional step I also did was to have what Nextcloud calls "pretty URLs"
Add these lines to the config.php file (https if you've secured your instance with certs, http if you haven't)
'overwrite.cli.url' => 'https://www.mydomain.com', 'htaccess.RewriteBase' => '/', 'overwriteprotocol' => 'https',Then from terminal, run this command.
sudo -u apache php /var/www/nextcloud/occ maintenance:update:htaccessMy URL then changed from
https://www.mydomain.com/nextcloudtohttps://www/mydomain.comand it removed the "index.php" from shared links.
