Parse-Server（Heroku部署）邮箱验证功能疑似Bug求助

It’s super frustrating when email verification doesn’t behave as expected—let’s break this down step by step to get to the bottom of what’s going wrong. Since you mentioned you’ve tried posting about this without luck before, let’s start with the most common culprits and work our way toward potential bugs.

First, let’s lock down that your core setup is solid. Here are key checks you can run right now:

1. Double-Check Your Email Adapter Configuration #

Take a close look at your emailAdapter settings in your Parse Server config (usually index.js or server.js). For example, if you’re using Mailgun:

emailAdapter: {
  module: 'parse-server-simple-mailgun-adapter',
  options: {
    fromAddress: 'no-reply@yourdomain.com', // Must match your verified provider domain
    domain: 'yourdomain.com', // Exact domain you set up in your email service
    apiKey: process.env.MAILGUN_API_KEY, // Confirm this env var is correctly set in Heroku
  }
}

• Make sure your email provider (Mailgun, SendGrid, etc.) has your Heroku app’s domain fully verified.
• Test sending a raw test email directly through your provider’s API to rule out service-side issues entirely.

2. Validate Heroku Environment Variables #

Misconfigured env vars are a frequent culprit. Run this in your Heroku CLI to list all active variables:

heroku config

Confirm these critical values are set correctly:

• SERVER_URL: Must be your full Heroku app URL (e.g., https://your-app-name.herokuapp.com/parse)—HTTPS is non-negotiable here, as most email providers block links from HTTP domains.
• APP_ID/MASTER_KEY: Match exactly what’s in your Parse Server config (no typos or extra spaces!).
• Email provider API keys/domains: Ensure they’re not missing, truncated, or using outdated credentials.

3. Dig Into Parse Server Logs #

Heroku logs will almost always tell you why emails aren’t sending or links aren’t working. Pull the latest logs with:

heroku logs --tail

Watch for errors like:

• Email adapter not configured (your adapter setup is incorrect)
• Failed to send email: [Specific error message] (direct issue from your email provider)
• Invalid server URL (your SERVER_URL is wrong, breaking the verification link)

4. Test the Verification Flow Manually #

If emails are sending but links fail:

• Check the verification link in the email—does it point to your Heroku app’s actual URL? If it’s using localhost or an old domain, that’s the problem.
• Try hitting the verification endpoint directly with curl to see if it returns a success:

  curl -X POST https://your-app-name.herokuapp.com/parse/verifyEmail \
    -H "X-Parse-Application-Id: YOUR_APP_ID" \
    -d "token=VERIFICATION_TOKEN_FROM_EMAIL&email=USER_EMAIL"
  

5. Rule Out Parse Server Version Bugs #

Older Parse Server versions have known issues with email verification. Check your current version:

npm list parse-server

If you’re on a version older than 5.0.0, consider upgrading to the latest stable release—many email-related bugs have been squashed in recent updates.

If All Checks Pass: It’s Likely a Bug #

If you’ve worked through all these steps and everything checks out, this could indeed be a reproducible bug. To help the community investigate:

• Post your full Parse Server config (redact sensitive keys like master keys or API keys)
• Share exact error logs from Heroku
• Provide your Parse Server version, email adapter type, and Heroku stack details

With that info, other developers can replicate your setup and pinpoint the issue quickly.

内容的提问来源于stack exchange，提问作者Michel