Docs

Troubleshooting

Solutions to common issues when setting up and using Nexting.

Verification Issues

HTTP 404: Not Found

The verification endpoint couldn't be reached on your domain.

Check configuration file

Ensure vercel.json (or equivalent) is in your project root

Wait for deployment

Deployments can take 1-2 minutes. Check your hosting dashboard for status.

Verify the path prefix

If your project has a path prefix (e.g., /blog), ensure it's included in the source path: /blog/__verify__

Test directly

Try visiting https://yourdomain.com/__verify__ in your browser

Project Key Mismatch

The verification endpoint returned a different project key.

Copy fresh configuration

Go to Settings and copy the configuration again. The project key may have been typed incorrectly.

Check for multiple projects

If you have multiple Nexting projects for the same domain, ensure you're using the correct key.

Page Display Issues

"Project Not Found" Error

The proxy couldn't find an active project for the given key.

  • Complete the verification process in Settings
  • Check that the project status is "Active"
  • Ensure the project key in your configuration matches exactly

"Page Not Found" Error

The project is active, but the specific page doesn't exist or isn't published.

  • Check that the page exists in your Nexting dashboard
  • Ensure the page status is "Published" (not Draft)
  • Verify the path matches exactly (case-sensitive)
  • If using a path prefix, ensure it's set correctly in both places

Wrong or Old Content

The page shows outdated content after you've made updates.

  • Content is cached for up to 5 minutes — wait and refresh
  • Try a hard refresh (Cmd/Ctrl + Shift + R)
  • Clear your browser cache or try incognito mode

Configuration Issues

JSON Syntax Error

Vercel deployment fails due to invalid JSON.

Common mistakes:

json
// ❌ Wrong - trailing comma
{
  "rewrites": [
    { "source": "/a", "destination": "..." },  // <- trailing comma not allowed
  ]
}

// ✅ Correct
{
  "rewrites": [
    { "source": "/a", "destination": "..." }
  ]
}
Use a JSON validator or your IDE to check syntax before committing.

Conflicting Routes

Your app has a page or API route at the same path as a Nexting page.

  • Remove or rename the conflicting file in your app
  • Use a different path prefix for Nexting pages
  • Note: Rewrites only apply when no matching file exists

Debug Checklist

Run through this checklist when something isn't working:

Still Need Help?

If you've tried everything above and still have issues, we're here to help.

Check the FAQContact Support