After install nextcloud and certbot
click here to request app password from the web interface
https://Domain/nextcloud/apps/files/?dir=/&fileid=127
The redirect should automatically generate at password and device username to which a user accepts.
I don't remember the exact URL name that should be expected.
https://Domain/nextcloud/apps/files/?dir=/&fileid=127
instead of requesting app password.@LexiconCode
Thanks for your report. I try to replicate.
Which Nextcloud desktop client you use? Linux, Windows or MacOS? Current version I assume?
I try to replicate on Stretch VM.
As we use (mostly) the Nginx configuration from https://docs.nextcloud.com, it is possible that this needs to be addressed to https://github.com/nextcloud/ directly. But let's investigate first.
@MichaIng
I'm using the Windows client the latest version. As long as the client supports the feature I assume it would be the same unexpected behavior across all client.
I can confirm this issue exists on Odroid NC2 and Odroid C2 running the same configuration.
Can confirm issue as well on Lighttpd and Apache2:
http://192.168.178.29/nextcloud/index.php/settings/personal?sectionid=security#apppasswords
http://192.168.178.29/nextcloud/index.php/apps/files/?dir=/&fileid=2
http://192.168.178.29/nextcloud/index.php/settings/user/security
I believe this is since the merge of user and admin settings. The initial link at least contains the old path scheme.
I opened a thread about it: https://help.nextcloud.com/t/windows-client-app-passwords-link-seems-to-be-obsolete/34116
GitHub issue opened: https://github.com/nextcloud/desktop/issues/514
Seems to be fixed with client version 2.5 (not yet released).
2.5 progress: https://github.com/nextcloud/desktop/projects/1
However I mark this topic as closed, as it's external and solved for next release.
€: Hmm, just tested current 2.5 daily. There is no such link any more. The client connects directly to Nextcloud via internal browser and allows to alternatively enter app token. But no link to token creation page... However the one or the other way, the issue is solved 😜.
Most helpful comment
GitHub issue opened: https://github.com/nextcloud/desktop/issues/514