Diya 🔥 fix(login): Fixed login issues#2182
Merged
Merged
Conversation
one-community
approved these changes
Apr 27, 2026
one-community
changed the title
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fixes login and API failures caused by CORS rejecting requests from the deployed frontend origins. The allowedOrigins set in cors.js only contained localhost entries, blocking all requests from the dev and production deployments.
Related PRS (if any):
None
Main changes explained:
startup/cors.js— added https://dev.highestgood.com and https://highestgoodnetwork.netlify.app to the allowedOrigins setHow to test:
Note:
This is a backend-only change. The Sentry issue HGN-MT-DEV-HEROKU-MMP (2K events, escalating) confirmed the missing origin. Only the origin is needed — no trailing slash or path.