Unable to grant access for sync client through Login Flow V2

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:


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


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, 12.0.2): 17.0.1
Operating system and version (eg, Ubuntu 17.04): Ubuntu 18.04
Apache or nginx version (eg, Apache 2.4.25): 2.4.38
PHP version (eg, 7.1): 7.3.11

The issue you are facing: The “Grant Access” page in my browser is unresponsive when I click the button after the page is opened by my sync client.
When I try on the android sync client, I get a 404 when I try to log in

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

Steps to replicate it:

  1. Download, install, and set up official Nextcloud docker image
  2. Point Linux sync client at server and let the browser page open
  3. Sign in
  4. Click “Grant Access”

The output of your Nextcloud log in Admin > Logging:

I saw no relevant output

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


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


Probably the generated urls are wrong. Please check overwritehost and overwriteprotocol.

Ok, thanks for the tip. I’m assuming you’re referring to config.php.

I found the line

'overwrite.cli.url' => 'http://cloud.mydomain.com'

where cloud.mydomain.com is my Nextcloud server. Does this need to be https or something?


UPDATE: I added the line

'overwriteprotocol' => 'https',

and seemed to have fixed things!