Repository navigation
FRONTEND_URL defaults to http://localhost:3001, but the Next.js frontend serves on :3000 — CORS and the OAuth redirect miss it #590
Description
Problem
configuration.ts and .env.example default FRONTEND_URL to http://localhost:3001. It's used both as the only CORS origin (enableCors({ origin })) and as the OAuth redirect target. next dev (MergeFi/frontend) runs on 3000, which is also this backend's own default PORT. A local setup that follows both READMEs gets CORS failures on every API call and an OAuth redirect to a port nothing listens on.
Suggested fix
Default the backend to PORT=4000 (which the frontend's NEXT_PUBLIC_API_URL already assumes) and FRONTEND_URL=http://localhost:3000, and update .env.example and the README.
Activity
tresjo81 commentedon Oct 13, 2026
Hi maintainers! I would like to take this on. I've checked the configuration setup: I will default PORT to 4000 and FRONTEND_URL to http://localhost:3000 in configuration.ts, update .env.example, and adjust the README so local setups align with Next.js out of the box. Ready to start and submit a clean PR right away upon assignment.
AminMG044 commentedon Oct 19, 2026
@AminMG044 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @AminMG044 to this issue.
yodakkak commentedon Oct 19, 2026
@yodakkak has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @yodakkak to this issue.
devpeter999 commentedon Oct 19, 2026
@devpeter999 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @devpeter999 to this issue.
drips-wave commentedon Oct 19, 2026
Congratulations, @devpeter999! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @devpeter999: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
grantfox-oss commentedon Oct 20, 2026
🎉 This issue has been marked as completed on GrantFox!
@devpeter999's PR #709 was approved and merged by @chonilius.
🏆 @devpeter999: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (411 total points). Track your full progress on GrantFox.
👏 Great work, @devpeter999! Keep contributing to MergeFi.
drips-wave commentedon Oct 20, 2026
This issue has been completed by @devpeter999 as part of the Stellar Wave Program's 10th Wave 🥳
😎 @devpeter999: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
fix: update frontend url, load relations in bounties, guard scheduler…