You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this is old - however, I ran into this as well. A common AWS setup is to run nginx as a reverse proxy for node. If you are also using a custom access_token header, nginx will not forward that header to node by default. You'll need to set underscores_in_headers on in the server section of the nginx config.
I can successfully authenticate with an access_token locally, but when performing the same action on remote url, it always returns 401 error.
Update: same server running on heroku works, not on AWS. Anyone run into this before?
The text was updated successfully, but these errors were encountered: