Wrong free space displayed

📱 Desktop & mobile clients 💻 Desktop
1
Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Nextcloud version (eg, 20.0.5): 20.0.9
Operating system and version (eg, Ubuntu 20.04): Debian 10.9.0
Apache or nginx version (eg, Apache 2.4.25): latest Apache Version
PHP version (eg, 7.4): 7.4

The issue you are facing:

Hello there.

We are currently faceing the Problem, that one User has to Login after every Restart of th Nextcloud-Client. Has anybody seen this behaviour before, and maybe has a solution for this?

Best regards Paul

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

I can’t replicate it myself now

The output of your Nextcloud log in Admin > Logging:

PASTE HERE

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

PASTE HERE

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE
2

I’ve seen this on one Linux Mint client in the past - say early 3.0 release. I don’t remember the solution but I know I identified the issue using the client logs… maybe this was related to Gnome keyring which was not present and client insisted on using it… forgive me no more details…

As the issue occurs on one client only you should double check how this client differs from working (software versions, settings) and compare client logs of good/bad clients… you could try logging in as known working user from the faulty client and faulty user on working client - this helps you understand if the problem related to user settings or occurs generally on specific machine.