Skip to content

requestPasswordReset email link (“Verify Email” button) redirects to Not Found #9995

Description

@rjcodedev

New Issue Checklist

Issue Description

When calling Parse.User.requestPasswordReset(...) from the Parse JavaScript SDK, the password reset email is delivered successfully, but the CTA button/link in the email (labeled “Verify Email”) redirects to a Not Found page when clicked.

Working fine with parse-server version : 8.6.2 and below

Steps to reproduce

  1. Trigger the password reset request using the Parse JS SDK:
    await Parse.User.requestPasswordReset(username);
  2. Open the password reset email you receive.
  3. Click the “Verify Email” button/link in the email.
  4. Observe that it redirects to a Not Found page.

Actual Outcome

Clicking the email CTA (“Verify Email”) opens a URL that results in Not Found.

Expected Outcome

Clicking the link in the password reset email should open the Parse Server password reset page/route, allowing the user to set a new password successfully.

Environment

Server

  • Parse Server version: 9.x.x
  • Operating system: Windows
  • Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local

Client

  • SDK (iOS, Android, JavaScript, PHP, Unity, etc): Javascript
  • SDK version: 8.0.0

Logs

Image

Activity

  1. parse-github-assistant commented on Dec 29, 2025

    @parse-github-assistant

    🚀 Thanks for opening this issue!

    ℹ️ You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

  2. coderabbitai commented on Dec 29, 2025

    @coderabbitai

    📝 CodeRabbit Plan Mode

    Generate an implementation plan and prompts that you can use with your favorite coding agent.

    • Create Plan
    Examples

    🔗 Similar Issues

    Related Issues

    🔗 Related PRs

    #9906 - feat: Add beforePasswordResetRequest hook [merged]

    👤 Suggested Assignees

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  3. mtrezza commented on Dec 31, 2025

    @mtrezza
    Member

    What is the URL? What's the exact Parse Server version?

  4. added
    type:bugImpaired feature or lacking behavior that is likely assumed
    on Dec 31, 2025
  5. rjcodedev commented on Dec 31, 2025

    @rjcodedev
    Author

    @mtrezza

    After calling await Parse.User.requestPasswordReset(username);, I was redirected to the following URL when I clicked the “Verify email” button.

    I have mounted parse-server on /app instead of /parse

    parse-server version : 9.1.1
    parse js sdk: 8.0.0

  6. SteffenKeller commented on Jan 7, 2026

    @SteffenKeller

    I am encountering the same problem on Parse Server 9.x The request_password_reset and also the verify_email endpoint returning 404 Not Found instead of redirecting to my custom pages after button is clicked in the email.

    The user email still gets verified so I guess the redirect to the custom page is the problem here.

    I have also mounted the server on /app instead of /parse.

    The Not Found URLs look like this:

    • https://<my_public_server_url>/app/apps/<my_application_id>/request_password_reset?token=abc123
    • https://<my_public_server_url>/app/apps/<my_application_id>/verify_email?token=abc123

    The custom pages are defined as follows:

    customPages: {
          invalidLink: 'https://<my_website_url>/invalid-link',
          linkSendFail: 'https://<my_website_url>/invalid-link',
          choosePassword: 'https://<my_website_url>/choose-password',
          linkSendSuccess: 'https://<my_website_url>/link-send-success',
          verifyEmailSuccess: 'https://<my_website_url>/verify-email-success',
          passwordResetSuccess: 'https://<my_website_url>/password-reset-success',
          invalidVerificationLink: 'https://<my_website_url>/invalid-link',
          expiredVerificationLink: 'https://<my_website_url>/expired-verification-link',
          invalidPasswordResetLink: 'https://<my_website_url>/invalid-link',
      }
    
  7. SteffenKeller commented on Jan 7, 2026

    @SteffenKeller

    Since the PublicAPIRouter was replaced with the new PagesRouter in Version 9 the custom pages must be defined as follows:

        pages: {
            customUrls: {
                emailVerificationSuccess: 'https://<my_website_url>/verify-email-success',
                emailVerificationSendFail: 'https://<my_website_url>/invalid-link',
                emailVerificationSendSuccess: 'https://<my_website_url>/link-send-success',
                emailVerificationLinkInvalid: 'https://<my_website_url>/invalid-link',
                emailVerificationLinkExpired: 'https://<my_website_url>/expired-verification-link',
                passwordReset: 'https://<my_website_url>/choose-password',
                passwordResetSuccess: 'https://<my_website_url>/password-reset-success',
                passwordResetLinkInvalid: 'https://<my_website_url>/invalid-link'
            }
        },
    

    Another breaking change is that the search parameter in the redirect url to the custom password reset page is now appId instead of id for the application id.

    Before: https://<my_website_url>/choose-password?id=<my_application_id>&token=...
    After: https://<my_website_url>/choose-password?appId=<my_application_id>&token=...

  8. mtrezza commented on Jan 12, 2026

    @mtrezza
    Member

    @SteffenKeller So is this merely a documentation issue?

  9. SteffenKeller commented on Jan 12, 2026

    @SteffenKeller

    Yes documentation issue for the custom pages, but shouldn't the server show a default page instead of a 404 if no custom pages are defined in the config?

  10. shayandutta commented on Jan 14, 2026

    @shayandutta

    I'd like to work on this issue. I've read the discussion regarding the potential appId vs id parameter mismatch in the password reset links. I'm going to start by setting up the local environment and writing a reproduction test case in /spec to confirm the 404 behavior. Once I have a failing test, I'll open a Draft PR. Can you please assign this to me?

  11. rjcodedev commented on Feb 2, 2026

    @rjcodedev
    Author

    hey @mtrezza ,

    Is there any update on the issue?

  12. rjcodedev commented on Feb 4, 2026

    @rjcodedev
    Author

    Can anyone help me with the code changes I need to make to get the code working?

  13. mtrezza commented on Feb 4, 2026

    @mtrezza
    Member

    Yes documentation issue for the custom pages, but shouldn't the server show a default page instead of a 404 if no custom pages are defined in the config?

    Correct

  14. 2 remaining items

  15. rjcodedev commented on Feb 6, 2026

    @rjcodedev
    Author

    hey @mtrezza ,

    still same issue in 9.2.1-alpha.1
    This URL is send to email for password reset
    http://localhost:8080/app/apps/product/request_password_reset?token=mLa7IcjWdHVaGJKKDrnjEjT3C

    In v8.6.2
    below URL is send to email for password reset and it's working fine
    http://localhost:8080/app/apps/choose_password?token=By0PEOC6psN1yPKG2x3rJVBFe&id=product&app=product

    Image
  16. mtrezza commented on Feb 6, 2026

    @mtrezza
    Member

    @rjcodedev Thanks for testing this out and providing more details. We're working on a fix and I'll update here.

  17. reopened this on Feb 6, 2026
  18. mtrezza commented on Feb 6, 2026

    @mtrezza
    Member

    @rjcodedev @SteffenKeller could you please confirm on which OS you are running Parse Server when encountering the 404 issue for default email verification pages? You are both running it on Windows? We have released an alpha version with a new fix. Could you please try it out.

  19. SteffenKeller commented on Feb 6, 2026

    @SteffenKeller

    @mtrezza I am running the server on Linux. For me the problem was fixed after I adapted the config change for the custom pages from customPages to pages.customUrls since I am not using the default pages anyway. If testing is still needed I can try out the new alpha without custom pages set in the config.

  20. mtrezza commented on Feb 6, 2026

    @mtrezza
    Member

    @SteffenKeller thanks, maybe @rjcodedev could try out 9.3.0-alpha.2 since he is able to reproduce the issue.

  21. rjcodedev commented on Feb 9, 2026

    @rjcodedev
    Author

    hey @mtrezza ,

    I am using windows
    after update to 9.3.0-alpha.2 error got changed
    http://localhost:8080/app/apps/product/request_password_reset?token=JVrK8BgRJImuGSzGBsBpte1Ad

    Image

    also now I am getting error in logs

    TypeError [ERR_INVALID_CHAR]: Invalid character in header content ["x-parse-page-param-appname"]
        at ServerResponse.setHeader (node:_http_outgoing:703:3)
        at ServerResponse.header (C:\new\apps\product\node_modules\express\lib\response.js:686:10)
        at C:\new\apps\product\node_modules\parse-server\lib\PromiseRouter.js:167:17
        at Array.forEach (<anonymous>)
        at C:\new\apps\product\node_modules\parse-server\lib\PromiseRouter.js:166:39
    
  22. mtrezza commented on Feb 9, 2026

    @mtrezza
    Member

    The issue may be related to your app name. Does it contain any chars outside of regex [a-zA-Z0-9]+? Maybe you could reveal just these chars, if it's not revealing your full app name. You could set a breakpoint to inspect what the invalid header value is.

    In any case, I just tested this out and the 9.3.0-alpha.3 release fixed the bug and shows the default page for password reset if pagesPath and customUrls aren't set. So I'm closing this issue. If you found more details regarding the app name, please open a new issue with more details about your app name, so we can check whether there's a separate issue with app name encoding.

  23. reopened this on Feb 9, 2026
  24. rjcodedev commented on Feb 10, 2026

    @rjcodedev
    Author

    Hey @mtrezza ,

    I don’t think there’s anything wrong with appname, since it works perfectly with version 8.6.2.

    Here are my credentials:

    appId = product
    appName = Product™

  25. mtrezza commented on Feb 10, 2026

    @mtrezza
    Member

    @rjcodedev This issue has been fixed. What you are describing seems to be a distinct issue. Feel free to open a new issue so we can investigate this. When you open a new issue, please provide an app name and the exact steps to reproduce the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

type:bugImpaired feature or lacking behavior that is likely assumed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions