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
{{ message }}
Repository navigation
requestPasswordReset email link (“Verify Email” button) redirects to Not Found #9995
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
Trigger the password reset request using the Parse JS SDK: await Parse.User.requestPasswordReset(username);
Open the password reset email you receive.
Click the “Verify Email” button/link in the email.
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
ℹ️ 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.
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.
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.
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?
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?
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?
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
@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.
@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.
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
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.
@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.
Activity
parse-github-assistant commentedon Dec 29, 2025
🚀 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.
coderabbitai commentedon Dec 29, 2025
📝 CodeRabbit Plan Mode
Generate an implementation plan and prompts that you can use with your favorite coding agent.
Examples
🔗 Similar Issues
Related Issues
🔗 Related PRs
#9906 - feat: Add
beforePasswordResetRequesthook [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:💬 Have feedback or questions? Drop into our discord!
mtrezza commentedon Dec 31, 2025
What is the URL? What's the exact Parse Server version?
rjcodedev commentedon Dec 31, 2025
@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
/appinstead of/parseparse-server version : 9.1.1
parse js sdk: 8.0.0
SteffenKeller commentedon Jan 7, 2026
I am encountering the same problem on Parse Server 9.x The
request_password_resetand also theverify_emailendpoint 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
/appinstead of/parse.The Not Found URLs look like this:
https://<my_public_server_url>/app/apps/<my_application_id>/request_password_reset?token=abc123https://<my_public_server_url>/app/apps/<my_application_id>/verify_email?token=abc123The custom pages are defined as follows:
SteffenKeller commentedon Jan 7, 2026
Since the
PublicAPIRouterwas replaced with the newPagesRouterin Version 9 the custom pages must be defined as follows:Another breaking change is that the search parameter in the redirect url to the custom password reset page is now
appIdinstead ofidfor 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=...mtrezza commentedon Jan 12, 2026
@SteffenKeller So is this merely a documentation issue?
SteffenKeller commentedon Jan 12, 2026
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?
shayandutta commentedon Jan 14, 2026
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?
rjcodedev commentedon Feb 2, 2026
hey @mtrezza ,
Is there any update on the issue?
rjcodedev commentedon Feb 4, 2026
Can anyone help me with the code changes I need to make to get the code working?
mtrezza commentedon Feb 4, 2026
Correct
2 remaining items
rjcodedev commentedon Feb 6, 2026
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=mLa7IcjWdHVaGJKKDrnjEjT3CIn 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=productmtrezza commentedon Feb 6, 2026
@rjcodedev Thanks for testing this out and providing more details. We're working on a fix and I'll update here.
mtrezza commentedon Feb 6, 2026
@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.
SteffenKeller commentedon Feb 6, 2026
@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
customPagestopages.customUrlssince 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.mtrezza commentedon Feb 6, 2026
@SteffenKeller thanks, maybe @rjcodedev could try out 9.3.0-alpha.2 since he is able to reproduce the issue.
rjcodedev commentedon Feb 9, 2026
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
also now I am getting error in logs
mtrezza commentedon Feb 9, 2026
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
pagesPathandcustomUrlsaren'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.rjcodedev commentedon Feb 10, 2026
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™
mtrezza commentedon Feb 10, 2026
@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.