when logged into my nextcloud server as user, I clicked to
User Bubble ->
Security and found a long list of entries below
Devices & sessions.
After searching the issue list, I found this issue ticket.
The issue is know but either it is a kind of special issue ore no one really cares about it.
There is currently no real solution but I want to offer a temporary one.
You can create a cronjob that executes the following sql statement once per week or day.
--- You have to replace <user_name> with your user name
`uid` = <user>
AND `last_activity` < UNIX_TIMESTAMP(DATE_SUB(CURRENT_DATE(), INTERVAL 16 DAY));
OPTIMIZE TABLE `oc_authtoken`;
From my point of view, it looks like Firefox is doing something strange. Maybe other browsers behave the same.
So today I wanted to quickly setup a public shared link so that a friend of mine is able to easily upload a file to me.
Of course, I've stumbled over the file drop but I was not able to find the "File drop (upload only" section when I was creating this share.
I tried to find more information and was digging into the documentation. I was going through the issue list but at the end, I was not able to fix the missing option. I was also quickly updating the server to the latest version, but also, no "File drop" selection.
Than, after reading the logs, investigating the
config.php, I finally found the missing link.
As an administrator, you have to go to
Sharing and check the
Allow public uploads configuration setting. After that, you can finally create your share as a user known as "file drop".
As written in the official issue ticket, following the way how to solve your conflict locally.
A quick update to figure out the conflicted files.
cd into your nextcloud synchronized path
#list conflicted files
find . -iname *conflic* -type f
You can than decide which file is the one you want to keep
foo (conflicted copy 2020-09-09 083407).bar.
See also here and here.
So, nextcloud version 15.0.x is out already and whenever you are logging into your next cloud with your administrator account, you still get this "you are on the latest version" message.
Further more, you just got a update to version 14.0.x while waiting for version 15.0.x.
To fix this, all you have to do is to switch from the channel "stable" to "beta".
After a page reload, you should see a version 15.0.x available.
Do the upgrade and do not forget to switch back to the stable channel.