Signup has three stages, and it can break at any of them. The form (does the request get sent?), the server creating the account (does it return an error?), and the confirmation or welcome email (does it arrive?). Try signing up with a fresh email address while watching the browser's Network tab. If the account is created but people can't continue, the confirmation email is usually the problem.
What's the problem
New users can't register, see an error, never get the confirmation email, or are told the email is already in use when it isn't.
Why it happens
- Form or script problems stopping the request.
- Server errors creating the account: database problems, a validation rule, or a recent code change.
- Captcha or bot protection blocking real people.
- Confirmation emails not delivered, or landing in spam.
- Leftover accounts from earlier failed attempts, so the email looks "taken".
- Payment or plan setup steps failing, for paid signups.
How to fix it
- Sign up yourself with a new address and watch the Network tab.
- If the request fails, read the response and the server logs.
- If the account is created but no email arrives, check your email service's logs and your domain's SPF and DKIM records. See emails not sending.
- Check captcha and firewall logs for blocked signups.
- Clear out half-created accounts or let people resend the confirmation.
What Preventionlabs checks
One click runs the full report on your domain. For this problem it shows whether your site loads, how fast, and where its redirects go; up to 50 pages from your sitemap, listing any that fail or are slow, plus broken links on them. With Cloudflare connected, it also shows which pages returned server errors (5xx) to visitors, and when; which requests the firewall blocked, by Cloudflare's own rule names; recent deploys and account changes, with their times. It doesn't fill in forms, log in or make payments, so test the feature yourself as well.
Run your free reportYour first report is free, no card needed. Then A$50 a month, up to 10 domains. Read-only: it never changes anything.
Sources
- MDN Web Docs: HTTP response status codesreference
HTTP response status codes indicate whether a specific HTTP request has been successfully completed.
- Google: Email sender guidelineshelp center
Set up SPF or DKIM email authentication for your sending domains.