859
edits
Changes
From SME Server
Jump to navigationJump to search→Known issues
=== Uninstall ===
=== Uninstall ===
yum remove {{#var:smecontribname}} {{#var:contribname}}
yum remove {{#var:smecontribname}} {{#var:contribname}}
=== Use a dedicated domain to connect to Nextcloud ===
<syntaxhighlight lang="bash">
db domains set cloud.mydomain.com domain Description "Nextcloud" Content Primary Nameservers internet TemplatePath WebAppVirtualHost DocumentRoot /usr/share/nextcloud RequireSSL enabled letsencryptSSLcert enabled
signal-event domain-create cloud.mydomain.com
#only if you use a Let's Encrypt certificate
expand-template /etc/dehydrated/domains.txt
dehydrated -c
#to let nextcloud accept this domain
OCC "config:system:set trusted_domains 10 --value=cloud.mydomain.com "
</syntaxhighlight>
=== Mount with davfs on Fedora Clients ===
=== Mount with davfs on Fedora Clients ===
echo "https://example.com/nextcloud/remote.php/webdav your_Nextcloud_username your_password" >> ~/.davfs2/secrets
echo "https://example.com/nextcloud/remote.php/webdav your_Nextcloud_username your_password" >> ~/.davfs2/secrets
chmod 0600 ~/.davfs2/secrets
chmod 0600 ~/.davfs2/secrets
</syntaxhighlight>then just mount ! you should see the folder mount at every logon from now on, if you do not want that, change "auto in the fstab by noauto.<syntaxhighlight lang="bash">
</syntaxhighlight>then just mount ! <syntaxhighlight lang="bash">
mount ~/nextcloud
mount ~/nextcloud
</syntaxhighlight>
</syntaxhighlight>
From there you can tweak the cache configuration to make it easier for you if you are far from the server, default cache size is 50MiByte, you could increase it to let's say 3 GiByte in ~/.davfs2/davfs2.conffor your user
From there you can tweak the cache configuration to make it easier for you if you are far from the server, default cache size is 50MiByte, you could increase it to let's say 3 GiByte in ~/.davfs2/davfs2.conf for your user <syntaxhighlight lang="bash">
cache_size 3G
</syntaxhighlight>you should see the folder mount at every logon from now on! if you do not want that, change "auto" in the fstab by "noauto".
Then add the following in ~/bash_profile or ~/bash_rc. You could user also mount -a and to try to put something in /etc/gdm/PostLogin/" instead<syntaxhighlight lang="bash">
mount /home/username/nextcloud
</syntaxhighlight>And Finally to umount in gdm using "sudo vim /etc/gdm/PostSession/"<syntaxhighlight lang="bash">
if [ ${USERNAME} = "myuser" ];then
umount -fl /home/myuser/nextcloud
fi
</syntaxhighlight>
Adapted from those sources:
Adapted from those sources:
repeat above for each major update until you are one update from the latest major update. At that point you can follow the usual process. source (https://bugs.contribs.org/show_bug.cgi?id=10670#c3)
repeat above for each major update until you are one update from the latest major update. At that point you can follow the usual process. source (https://bugs.contribs.org/show_bug.cgi?id=10670#c3)
==== Upgrading from 17.0.1.x to 17.07.x ====
You can use the built in updater.
The only issue experienced was right at the end of the process with a http 500 error. I just did 'retry' and it completed.
You may need to update your database which I did as follows - note it may take a very long time with a lot of files:
OCC maintenance:mode --on
OCC db:convert-filecache-bigint
OCC maintenance:mode --off
==== User cannot see shares/files ====
After a new install the admin user could see shares but not a user.
We had a single ibay and it was set:
Group Everyone
Write group
Read everyone
We created a new group called localusers and added the admin and single user.
We then set the ibay:
Group localusers
Write group
Read group
This appeared to fix the issue and the user could now see the files.
=== Bugs ===
=== Bugs ===
