Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Cross-Origin Request Blocked #1529

Open
SnowyTheVampire opened this issue Jan 10, 2023 · 2 comments
Open

[Bug] Cross-Origin Request Blocked #1529

SnowyTheVampire opened this issue Jan 10, 2023 · 2 comments
Assignees
Labels
Gauzy GitHub type: bug 🐛 Something isn't working type: question ❓ Further information is requested
Milestone

Comments

@SnowyTheVampire
Copy link

SnowyTheVampire commented Jan 10, 2023

Bug Report

Hi, this is more personalized to a fork of ever-demand than the origin, so I apologize in advance. I did reach out on discord for the best tangible means of asking for assistance. I've tried to replicate ever-demand mostly for educational purposes, with the hope to find a tangible ecommerce solution at the same time.

The first issue I experienced was with MongoDB localhost, that I solved by changing the http:// links from localhost to 127.0.0.1, due to it wanting to handshake on ipv6 (::1) instead of ipv4...

But the second issue which I am currently stuck on is an error thrown in browser, during yarn run:server and run:shopweb, stating: "Cross-Origin Request Blocked: The Same Origin policy disallows reading the remote resource at http;//****. (Reason: CORS header 'Access-Control-Allow-Origin' missing). Status code: 200."

🔎 Search Terms

Cross-Origin Request Blocked
Socket.io + Node.js Cross-Origin Request Blocked
How to fix this CORS issue in socket.io?

🕗 Version & Regression Information

  • This is a bug in azure live development browser window
  • This is the development fork of ever-demand
  • I tried creating a build of the master branch, but had several bugs that were overtly difficult with my limited knowledge and ultimately went back to the development branch.

🙁 Actual behavior

After fresh installing Node + everything that's bundle with it (npm, python, Microsoft tools, etc), globally re-installing yarn latest, installing MongoDB, running 'yarn install' within the relevant origin folder to download dependencies, running 'yarn build:all' and launching the servers with 'yarn run:server' and 'yarn run:shopweb', I am greeted with working environments. (I had better luck with 'yarn install', than trying to use 'yarn bootstrap', 'yarn lerna bootstrap' or npm installing lerna globally).

However, when i connect to localhost:4200, which both 'yarn run:shopweb' and 'yarn run:admin' are wanting to load onto (shopweb not running on 3000 for some reason?), I am greeted with the Cross-Origin Request Blocked error. This is a repeating error that is preventing then sending and receiving of information.

Screenshot: firefox_eiAAD6J6ed

Edit: Random paragraph duplication made it illegible

@evereq evereq self-assigned this Jan 10, 2023
@evereq evereq added the type: question ❓ Further information is requested label Jan 10, 2023
@evereq evereq added this to the v0.3 milestone Jan 10, 2023
@djriffle
Copy link

I'm experiencing the same issue, has there been any progress on this?

@evereq
Copy link
Member

evereq commented Feb 3, 2023

@SnowyTheVampire @djriffle are you running all in http, without https? And all runs on 127.0.0.1? From screenshot, it's not clear what URL you try to open in browser, only clear that it tries to connect to socket.io server running on port 5500 on 127.0.0.1... So it means that issues are to connect from admin / web shop to socket.io host?

@evereq evereq changed the title Cross-Origin Request Blocked [Bug] Cross-Origin Request Blocked Feb 8, 2024
@evereq evereq added the type: bug 🐛 Something isn't working label Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Gauzy GitHub type: bug 🐛 Something isn't working type: question ❓ Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants