Persistent password-reset rate limit and signup failure on apps.nextcloud.com

Đang mở
  • Có gì không ổn?
#1,948 1 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
4/5
Thời gian dự kiến
3-5 ngày
Mức phù hợp với người mới
25/100
Loại issue
Lỗi
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
django, python
Lĩnh vực
authentication, backend

Hướng nghiên cứu

The report describes password recovery and signup failures but names no code files, tests, or confirmed cause. Start by reading the recovery and registration entry points and checking relevant server logs or tests to locate the failure. Done means eligible users can recover access after the documented limit expires and signup returns a useful result; the issue also asks maintainers for account-specific guidance.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.
Steps to reproduce
  1. Initial login attempts at https://apps.nextcloud.com/login/ fail with the message that the username and/or password is incorrect.
  2. Attempt account recovery at https://apps.nextcloud.com/password/reset/. The site displays the German message “Verboten – Zu viele Versuche. In einigen Minuten erneut versuchen.”
  3. The same recovery error was observed on 11 October 2026 and is still reported on 12 October 2026. An attempted registration at https://apps.nextcloud.com/signup/ also fails, described as a server error or an abort without a useful message.

These are observations from existing attempts, not a request to repeat them. The exact request-free interval between attempts and the HTTP status of the failed form submissions have not been captured.

Expected behaviour

Account recovery should be available once the documented request limit has expired. If a limit still applies, the interface should provide an actionable explanation or recovery channel. Registration should return an understandable validation message or complete successfully for eligible details.

Actual behaviour

Password reset remains blocked by the too-many-attempts message. Registration fails without useful guidance. The initial incorrect-credentials message does not establish which credential is wrong. I cannot currently recover access to the App Store.

I have already tried both Google Chrome and Safari, as well as an incognito/private browsing mode, without resolving the problem. This is my report of earlier attempts; these attempts were not repeated for this issue draft.

Two separate unauthenticated GET checks of the reset and signup form pages on 12 October returned HTTP 200. These checks did not submit either form and do not establish that account actions or my browser session work. No claim of a general outage or a specific rate-limit cause is made.

Could you check whether there is a known issue affecting recovery or registration, explain the expected recovery wait, and advise the appropriate private channel if account-specific details are needed?

Browser

Browsers tested: Google Chrome and Safari. Incognito/private browsing was also tried. These attempts did not resolve the issue; a complete matrix of each action and mode was not recorded.

Browser version: Not yet collected.

Operating system: macOS; exact version not yet collected.

Browser log / JavaScript Console Output

No browser console or failed-request network log has been collected. No additional login, reset or signup submission was made for this report.

Ngôn ngữ chính
Python
Star
398
Fork
180
Merge trung bình
2 ngày 15 giờ
Pull request đã merge (30 ngày)
15

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của nextcloud/appstore

Tất cả issue của nextcloud/appstore

Issue tương tự

Thêm issue về Python

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.