Desktop client suddenly needs to be authenticated in browser after every reboot

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.11
Operating system and version (eg, Ubuntu 20.04): Various, macOS Mojave/Catalina/Big Sur
Apache or nginx version (eg, Apache 2.4.25): nginx/1.14.2
PHP version (eg, 7.4): PHP 7.3.29-1

The issue you are facing:

I have the desktop app installed on a few machines with open at startup where they all used to just log in automatically after a reboot. But now I’m getting lots of sync errors because I keep working on these machines and realise later the nextcloud wasn’t authenticated after a reboot and seems to require the browser authentication every time.
I’m using Version 3.2.1 (macOS).

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

Steps to replicate it:

  1. Reboot any OS connected to Nextcloud server via Desktop app

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

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'memcache.distributed' => '\\OC\\Memcache\\Redis',
  'redis' =>
  array (
    'host' => 'redis',
    'port' => 6379,
  ),
  'datadirectory' => '/data',
  'trusted_proxies' =>
  array (
    0 => 'swag',
  ),
  'overwritewebroot' => '/nextcloud',
  'overwrite.cli.url' => 'https://xxxxxxxxx.org/nextcloud',
  'trusted_domains' =>
  array (
    0 => 'xxxxx.duckdns.org',
    1 => 'xxxxxxxxxlocal',
  ),
  'instanceid' => 'xxxxxxxxxxxx',
  'passwordsalt' => 'xxxxxxxxxxxxxxxx',
  'secret' => 'xxxxxxxxxxx',
  'dbtype' => 'mysql',
  'version' => '20.0.11.1',
  'dbname' => 'nextcloud',
  'dbhost' => 'nextclouddb',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'xxxxxxxx',
  'dbpassword' => 'Yxxxxxxxx',
  'installed' => true,
  'maintenance' => false,
  'loglevel' => 2,
  'mail_from_address' => 'xxxxxx',
  'mail_smtpmode' => 'smtp',
  'mail_sendmailmode' => 'smtp',
  'mail_domain' => 'xxxxxx',
  'mail_smtpauthtype' => 'LOGIN',
  'mail_smtpauth' => 1,
  'mail_smtphost' => 'xxxxxxx',
  'mail_smtpname' => 'xxxxxxxxxxxx',
  'mail_smtppassword' => 'xxxxxxxxxxx',
);

I got the same issue on MacOS Monterey.
After upgrading at any reboot is a new authentication required.
How can i fix it ?

Would anyone like to comment here? Is this just something we have to live with now? Or is their something wrong with the way we have things set up?

It’s quite annoying as the browser popup can be easily missed and you can be thinking you are working with a synced folder when in fact you are not.

So just tested on 1 iMac (Big Sur),
1 MacBook Pro (Catalina) ,
1 MacBook Pro (Mojave),
1 Hackintosh (Catalina)

All of them require reauthentication on boot.
This really sucks.
Is this like fight club where we’re not allowed to talk about it?

There is a an closed issue. Nobody wrote something. You can open an issue and perhaps link it to the old issue. Also perhaps some MacOS fans read this.

I added a comment on the existing issue. I am seeing this with macOS 12.

A perhaps-helpful datapoint. I updated the mac to nextcloud desktop 3.5.3 and on starting NC, it synced without asking for auth. But starting is a different path than restart after crash. Will see how the next power failure goes :slight_smile:

So this is still happening after upgrading to NC client 3.3.5 on all systems.

So just tested on 1 iMac (Big Sur),
1 MacBook Pro (Catalina) ,
1 MacBook Pro (Monterey),
1 Hackintosh (Catalina)

add to that list I guess these users on Linux

Seriously what’s up with this?