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

Proxy port not set correctly #163

Open
JosephSemrai opened this issue Dec 28, 2019 · 1 comment
Open

Proxy port not set correctly #163

JosephSemrai opened this issue Dec 28, 2019 · 1 comment

Comments

@JosephSemrai
Copy link
Contributor

JosephSemrai commented Dec 28, 2019

Describe the bug
Initially, the frontend will not be able to send requests to the backend (tested through the login and register routes). This is because all requests are proxied to the port 4000, but the backend (both dev and production) are running on port 3000 by default.

This leads to all requests failing to be fulfilled.

To Reproduce
Steps to reproduce the behavior:

  1. cd labellab-client
  2. npm install
  3. npm start
  4. New terminal window
  5. cd labellab-server
  6. npm install
  7. npm start or npm run dev
  8. Perform any request on the frontend and observe the error in the frontend console log.

Expected behavior
Requests are fulfilled by the backend.

Screenshots
image
Backend starting on port 3000
image
image
Proxy pointing to the wrong port

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Chrome
  • Version: 80

Additional context
Should be solved by updating the proxy value. I can make a pull request for this, given permission.

@Tushar19varshney
Copy link
Contributor

package.json is updated now and I have removed the proxy port. If you want to add proxy config you can make PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants