Skip to main content
If something isn’t working as expected in Lynkz, these common issues and solutions should help you get back on track.
  • IP lockouts last 24 hours — wait and try again once the period has elapsed.
  • If you have a recovery email set, use the “Forgot PIN?” flow on the login screen to receive a magic link and regain access immediately.
  • Without a recovery email, there is no bypass. Your only option is to create a new page with a different username.
  • Verify your Firestore rules are published. Go to Firebase Console → Firestore → Rules and confirm the rules match those in the Firestore Rules guide, then click Publish.
  • Confirm all NEXT_PUBLIC_FIREBASE_* variables are set correctly in your .env.local file — a missing or misspelled variable will prevent the client SDK from connecting to the right project.
In Vercel, adding or changing environment variables does not automatically apply to your running deployment. After adding or updating any variable in the Vercel dashboard, trigger a new deployment for the changes to take effect.
  • FIREBASE_SERVICE_ACCOUNT_KEY must be the full JSON string copied from your downloaded service account file — not a file path.
  • Never commit this value to your repository. Set it only as a Vercel environment variable in the dashboard.
  • Check whether the link has a schedule configured. Links with a start or end datetime are hidden automatically when viewed outside that window.
  • Confirm that NEXT_PUBLIC_APP_URL is set to your production URL in your Vercel environment variables.
  • If you’re using a custom domain, make sure it is pointed to the correct Vercel deployment and that the domain is fully propagated.
If your issue isn’t listed here, open an issue on GitHub.