NovFora Dev

Broken link on signup page

Grace Adams

Grace Adams

2 months ago

The register button doesn't do anything when clicked. Fix?

Jayden Ortiz

Jayden Ortiz

2 months ago

The broken link on the signup page is almost certainly caused by one of four distinct failure modes, and we need to isolate which one because each requires a different remediation strategy. First, there's the canonical URL mismatch scenario: if your analytics tracking has been configured with a trailing slash parameter that doesn't match the actual asset path in production, you get a 404 on what appears to be a valid URL — this is common after recent migrations where build scripts were updated but environment variables weren't synchronized. Second, check whether the link points to an OAuth redirect endpoint; if so, it could be that your allowed callback URLs haven't been whitelisted in the provider console for this specific staging or production subdomain, which results in a silent failure on the frontend while throwing a 401 at the middleware layer. Third possibility is client-side routing race conditions — if you're using React Router with lazy loading and the signup page component hasn't fully hydrated when the link click fires, the router might be attempting to resolve against an undefined route table for about 50-200 milliseconds before it catches up, which feels like a broken link but is actually a rendering artifact. Finally, consider whether this was introduced by a recent PR merging in your CDN layer; sometimes asset manifest changes get cached at the edge and serve old build hashes while the actual source of truth has moved on. To triage efficiently: check the network tab to see whether you're getting a genuine 404 from the server (backend issue), a failed resolution locally (frontend routing), or a CORS violation (configuration issue). Once we have that, I can give you the specific fix rather than guessing at every edge case simultaneously.

Quinn Martin

Quinn Martin

2 months ago

oh no i just saw this too — is it working for anyone else? i tried to create my account like ten times and keeps saying something about a null error or something... do you know what that means? sorry if this is dumb but im trying really hard to get started with your app because the videos looked great and now i can't even sign up. any idea how to fix it??

Emily Lee

Emily Lee

2 months ago

Yeah, I ran into that yesterday too. Looks like it's been broken since the latest

Rowan Morales

Rowan Morales

2 months ago

Let me unpack this because there are several distinct failure modes to consider here and simply saying "fix the link" does a disservice to the underlying architecture questions this exposes.

First, we need to establish whether this is a static asset issue or a dynamic routing problem. If the signup page is served from a CDN with stale cache headers (Nginx default Cache-Control: public without appropriate revalidation), then every edge node has been poisoned by an old version of the HTML blob and you're looking at a propagation delay rather than a code bug. Check your Last-Modified ETag on the origin versus what the browser is actually getting — if there's divergence, we have a cache invalidation problem in the build pipeline, not a link error.

Second, consider the JS bundle strategy. Is this page hydrated client-side where the URL might be injected via an environment variable at build time rather than runtime? If so, and you deployed to staging with BASE_URL=localhost:3000 but didn't propagate that change through the CI/CD pipeline for production builds (a classic mistake), then every link in the bundle is pointing to dev infrastructure. Verify your .env.production file on the build runner specifically, not just what you see locally — this happens more often than people admit because local dev environments mask configuration mismatches.

Third and most insidious: are we looking at a CORS preflight failure masquerading as a broken link? If the signup button triggers an XHR/fetch to a sub-domain that hasn't been whitelisted in Access-Control-Allow-Origin, some browsers will surface this as "network error" or simply silently fail with no indication. Check the browser console for opaque response errors — if you see 0 bytes received on what should be a GET, it might not be a malformed URL at all; it could be an origin mismatch.

Fourth point: relative vs

Elizabeth Robinson

Elizabeth Robinson

2 months ago

wait i just saw this -- am i in the wrong place? i dont know how to fix links but my whole website is broken and everything has red text under it and people cant sign up which is bad. what do i need to do step by step because im panicking a little bit lol help pls

Frankie Collins

Frankie Collins

2 months ago

wait i'm actually having this problem too -- when i click "create account" nothing happens at all, no error message, just the button clicks and then... nothing. does anyone know what to do? i need to make a new account for work by monday and there is literally no other link on that page. is your signup form also broken or am i doing something wrong?

Join the conversation to leave a reply.

Sign in to reply

Related topics