Common Issues
When Installing Fluxedita

Incorrect or broken .env values

Symptoms:

Errors during Vercel deployment or app crashes on load.

Most common causes:

• Extra spaces around keys (e.g., `SUPABASE_URL = https://...` instead of `SUPABASE_URL=https://...`)
• Missing variables entirely
• Using regular Gmail password instead of an App Password

Fix:

• Always copy/paste .env values with no spaces around the equals sign
• Use double quotes (`""`) only if your value contains special characters or spaces
• Use the `.env.example` file as your checklist
• Double-check you’re pasting values into both the local `.env` file AND Vercel’s Environment Variables section

Pro Tip: If the site breaks on Vercel but works locally, check for missing or mistyped .env values in your Vercel project dashboard.

Can’t find a file or folder in the code editor

Symptoms:

“Where is .env?” “Where are the SQL scripts?” “I can’t find pages/index.tsx…”

Fix:

• Use the file search shortcut in your code editor (e.g., VS Code): `Ctrl + P` (Windows/Linux) or `Cmd + P` (Mac)
• Then start typing the file name: `.env`, `supabase.sql`, `admin_promotion.sql`

Pro Tip: Don’t dig through folders — search is faster!

Supabase or Cloudinary API keys not found

Symptoms:

Auth errors, broken images, user creation fails, etc.

Fix:

• In Supabase: Go to your project → ⚙️ Settings → API. Copy anon key and project URL
• In Cloudinary: Dashboard → Account Details → Copy cloud_name, api_key, and api_secret

Pro Tip: If your images or videos don’t load, double-check your Cloudinary URL setup and that media is uploaded.

Email/SMTP not working

Symptoms:

The contact form doesn’t send messages.

Fix:

• Use Gmail App Passwords — not your Gmail login password
• Enable 2FA on your Gmail account before you can generate an app password
• Use the following .env setup:

• SMTP_HOST=smtp.gmail.com
  SMTP_PORT=465
  SMTP_USER=your@gmail.com
  SMTP_PASS=your_app_password

Pro Tip: You can test SMTP locally with a tool like Mailtrap if you're not ready for Gmail setup.

Git push fails or authentication errors

Symptoms:

`fatal: repository not found`, `Permission denied`, Push fails silently

Fix:

• Ensure your GitHub repo has no README or .gitignore if you're pushing an existing project
• Run these commands (if starting over):

• git init
  git add .
  git commit -m "First commit"
  git branch -M main
  git remote add origin https://github.com/YOUR_USERNAME/YOUR_REPO.git
  git push -u origin main

Pro Tip: If Git keeps asking for a username/password, consider setting up SSH keys.

Overwhelmed by command line? Use GitHub Copilot

Symptoms:

“I’m new to Git.” “I don’t know how to fix this error.” “I don’t know what this code means.”

Fix:

• Install GitHub Copilot in VS Code — it can:
• Auto-complete Git commands
• Suggest .env structure
• Help you write queries or modify code
• Detect missing or invalid syntax

Pro Tip: Think of Copilot as your personal assistant — type natural language comments like: `// create a section with a hero and slider component`

Vercel Deployment Fails Unexpectedly

Symptoms:

App won’t deploy, White screen or generic 500 error on first visit

Fix:

• Confirm the GitHub repo is public or connected
• Ensure all required .env variables are set correctly
• Verify that “Root Directory” in Vercel is empty unless your code is nested

Pro Tip: Check Vercel’s Logs tab for exact error messages. It’s very helpful.

Forgot to Promote Supabase User to Admin

Symptoms:

You can log in, but don’t have admin editing rights

Fix:

• Run the third SQL script: `promote_user_to_admin.sql`
• Replace the UUID in the query with your user’s UUID from Supabase Auth

Pro Tip: Your admin user should have both "admin" role and "premium" membership.

Unsure How to Build/Edit Sections

Symptoms:

You’re logged in, but don’t know how to use the page editor or add content.

Fix:

• Use the Page Editor and Sidebar to add new section components.
• All sections are modular and reusable.

Want to Customize Layout or Add Code?

Fix:

• Use the Custom Code Section to add HTML/CSS/JS directly via JSX.