You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a windows to enter a new password appears, enter a new password that satisfies the policy you set
Expected behaviour
The new password should be accepted and set, a confirmation should be displayed.
Actual behaviour
In Chrome, I get HTTP ERROR 405. In Firefox I get "Access deniedCSRF check failed". Unsure wether new password is set.
Server configuration
Operating system: Debian Stretch (up to date) Web server: Apache 2.4.10 Database: MySQL 5.5.58 PHP version: 5.6.30
Nextcloud version: 13.0.0 Beta 3 Updated from an older Nextcloud/ownCloud or fresh install: Upgraded from 12.0.4 Where did you install Nextcloud from: admin page / installer Signing status: no errors upon signing: http://example.com/index.php/settings/integrity/failed reports "No errors have been found." Warnings upon PGP 5.6 though. (BTW, what will happen to debian users in next debian version isn't released before NC 14?)
Web server error log: No entry while doing password reset.
But I see this:
[ssl:error] AH02032: Hostname www.seyfarth.de provided via SNI and hostname seyfarth.de provided via HTTP are different
Yet, Let's Encrypt seems to be correct:
Certificate Name: seyfarth.de
Domains: www.seyfarth.de seyfarth.de
Expiry Date: 2018-03-07 22:32:14+00:00 (VALID: 78 days)
Paths: ...
Nextcloud log (data/nextcloud.log): No entry while doing password reset.
Browser log: seems not relevant, is it?
The text was updated successfully, but these errors were encountered:
Fixes#7574
During some refactoring the event linked to password reset got removed.
This ment that we just submitted a normal POST but without the CSRF
token. And none of the js magic to redirect afterwards.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Is there some connection to the observations described in the first comment of nextcloud/contacts#453?
Might this (and other issues I encounter) be caused by an over-protective cross-site policy? Reason is the browser JS and the web server error log entries above, possibly caused by not honoring "Alternative DNS names" within the webserver TLS certificate?
Browser console:
Content Security Policy: Die Einstellungen der Seite haben das Laden einer Ressource auf self blockiert ("script-src 'nonce-NGRPZTRSdW45empjcHF3YUUwK0MwUXE3a1VrS3lWV2Fua3YrRXJOTldLUT06cTc2cTJFM2pyV3l3OVBaVFd6L3ovbWFPL25saG5SYko3VE9mS3Njdkdldz0=' 'unsafe-eval'"). Source: ondrop attribute on INPUT element. contacts
Webserver error log:
[ssl:error] AH02032: Hostname www.seyfarth.de provided via SNI and hostname seyfarth.de provided via HTTP are different
Let's Encrypt seems to be correct: Certificate Name: seyfarth.de, Domains: www.seyfarth.de seyfarth.de
Steps to reproduce
Expected behaviour
The new password should be accepted and set, a confirmation should be displayed.
Actual behaviour
In Chrome, I get HTTP ERROR 405. In Firefox I get "Access deniedCSRF check failed". Unsure wether new password is set.
Server configuration
Operating system: Debian Stretch (up to date)
Web server: Apache 2.4.10
Database: MySQL 5.5.58
PHP version: 5.6.30
Nextcloud version: 13.0.0 Beta 3
Updated from an older Nextcloud/ownCloud or fresh install: Upgraded from 12.0.4
Where did you install Nextcloud from: admin page / installer
Signing status: no errors upon signing: http://example.com/index.php/settings/integrity/failed reports "No errors have been found." Warnings upon PGP 5.6 though. (BTW, what will happen to debian users in next debian version isn't released before NC 14?)
List of activated apps:
Nextcloud configuration:
Are you using external storage, if yes which one: no
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: Firefox 57 / Chrome 63
Operating system: W10
Logs
Web server error log: No entry while doing password reset.
Nextcloud log (data/nextcloud.log): No entry while doing password reset.
Browser log: seems not relevant, is it?
The text was updated successfully, but these errors were encountered: