Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource

I am deploying forest admin on Elastic Beanstalk. And I am facing this issue "Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource’. I think it is the cores issue

app.use(function (req, res, next) {
   res.setHeader('Access-Control-Allow-Origin', '');
   res.setHeader('Access-Control-Allow-Methods', 'GET, POST, OPTIONS, PUT, PATCH, DELETE');
   res.setHeader('Access-Control-Allow-Headers', 'Authorization');
   res.setHeader('Access-Control-Allow-Credentials', true);

Than that error is resolved but I am facing unauthorized error.

Hi @rohit_ja,

that error is resolved but I am facing unauthorized error.

I’m glad the first error was resolved :confetti_ball: (side question: do you remember what was wrong and how did you fixed it?)

:point_right: Could you tell me more about this unauthorized error? You could edit your post by adding maybe:

  • The full error message
  • Your backend logs
  • A screenshot of the error in UI if any

I fixed the first error using this code:

app.use(function(req, res, next) {
  res.header("Access-Control-Allow-Origin", "*");
  res.header('Access-Control-Allow-Methods', 'GET, POST, OPTIONS, PUT, PATCH, DELETE');
  res.header("Access-Control-Allow-Headers", "Origin, X-Requested-With, Content-Type, Accept,Authorization");

But Now Whenever my API is called than in request Authorization token is not present.I don’t know why is this happened

Hello @rohit_ja :wave:

For your convenience, when you deploy an app anywhere and need to set CORS, you can use an environment variable called CORS_ORIGINS. In your case you can use CORS_ORIGINS= (I don’t know your provider, but setting an env variable can be done either in your remote instance configuration, or using the .env file :+1: )

Can you test again using this variable and removing the additional middleware please ?

Keep me in touch :raised_hands:

Thanks for the reply but still facing the same issue.
No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘’ is therefore not allowed access. The response had HTTP status code 504.

Hello @rohit_ja :wave:

This is strange, may I ask if you did any change to your generated project ?

I’m asking because by default, in the app.js file you should have something like this :

Which is the default and mandatory configuration to get CORS running.

Can you confirm these lines are present ?

yes it is present

Hello @rohit_ja :wave:

It is really strange, the code you added (mentioned earlier in the post) should not be necessary if you already have this config.

I tried to curl you remote instance to see if it was responding, it looks like the ssl certificate is not correct (self signed ?)

Also, I’ve seen that you are using EB from Amazon, it might require a little bit of config to get the CORS working properly.

Do you confirm your local project works correctly ?


yes it is working proper on my local

Hi @rohit_ja,

It is honestly hard to help you about your issue.
My understanding is that your CORS issue was supposed to be solved (according to your own response 5 days ago) and then it is not anymore (according to your response 4 days ago).

My feeling is that you should not add custom code for the CORS configuration and keep the Lumber generated default logic.
If you confirm that your project local environment works as expected, as Steve mentioned, it is probably an issue with your Elastic Beanstalk configuration.

Sorry for the silly questions, I am not an expert of AWS:

  • Do you have a reverse proxy or load balancer that could reject the Admin API requests?
  • Do you have a spot where you can/must configure your CORS in AWS interface?

Thanks you for your help.

Hi @rohit_ja,

Did you manage to solve your issue?