Front-End and Back-End Proxying is Insufficient to Remove CORS Errors

[anth-volk]

When attempting to launch this package, each attempt to fetch any existing user tokens and/or login failed with Error 403: Forbidden. I was only able to resolve these issues by installing and using cors middleware, then changing all relevant links to the actual back-end route instead of the port 3000 proxy that this app uses by default. This also required re-configuring the Spotify application dashboard to set the callback URI to the un-proxied address.

[ChrissaK]

I'm having exactly the same issue following this example: requests to http://localhost:3000/auth/* are not forwarded to http://localhost:5000/auth/*. Why is that? Is there a solution to this issue, except for using cors?

[anth-volk]

To be honest, I really don't know. I chocked it up to this package just being mostly unmaintained at this point, so perhaps the issues arose after the feature was introduced? But I haven't dug much deeper than that.