Fix/backend cors origin

[arpit2006]

Related Issue

• Closes: 🐛 Bug Report: Fix Incorrect Production Frontend Origin in CORS Allowlist #672
• Reference: 🐛 Bug Report: Fix Incorrect Production Frontend Origin in CORS Allowlist #672

---

Description

Fixed an incorrect production frontend origin in the backend CORS allowlist.

Changes Made

• Corrected the frontend deployment URL used in the CORS configuration.
• Ensured requests from the deployed frontend are properly accepted by the backend.
• Prevented production API calls from being blocked due to origin mismatch.
• Improved reliability of authentication and data-fetching requests in deployed environments.
• Reviewed CORS configuration to ensure compatibility with the current frontend deployment.

This fix resolves a production issue where browser requests could fail due to an invalid or outdated allowed origin.

---

How Has This Been Tested?

• Verified backend starts successfully after the change.
• Tested API requests from the deployed frontend.
• Confirmed CORS headers are returned correctly.
• Verified authentication and protected API routes function as expected.
• Checked browser developer tools to ensure no CORS-related errors occur.
• Confirmed local development environment remains unaffected.

---

Type of Change

• Bug fix
• New feature
• Code style update
• Breaking change
• Documentation update

[netlify]

✅ Deploy Preview for github-spy ready!

Name	Link
🔨 Latest commit	31173f6
🔍 Latest deploy log	https://app.netlify.com/projects/github-spy/deploys/6a1d899367be2e0008ae115e
😎 Deploy Preview	https://deploy-preview-673--github-spy.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Warning

Review limit reached

@arpit2006, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 43 minutes and 20 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0fc7a4f8-4afe-4612-a2ab-bbc276fd520b

📥 Commits

Reviewing files that changed from the base of the PR and between 53f820b and 31173f6.

📒 Files selected for processing (1)

• backend/server.js

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[arpit2006]

@mehul-m-prajapati , Requesting Review!