Your admin backend is unreachable. Please check that it is running and respond to http://forest.***.com

Expected behavior

Should be able to login in forest admin

Actual behavior

From the last couple of days some members of our team not able to login to the forest. It sometimes happened to me. It’s showing login pop-up and giving me an error saying Your admin backend is unreachable. Please check that it is running and respond to*
If I refresh(ctrl + f5) it was working but now it’s not.
I have checked my domain is working properly(http://forest.$$$.com).
I have allowed all origin(*) in cors setting

What is the current behavior?

Failure Logs

Please include any relevant log snippets, if necessary.
In browser console:
Access to XMLHttpRequest at '’ from origin ‘’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.
POST http://forest.
.com/forest/sessions net::ERR_FAILED


Please provide any relevant information about your setup.

  • Package Version: 2.16.9(forest-express-sequelize)
  • Express Version:4.16.2
  • Sequelize Version:4.37.10
  • Database Dialect: postgres
  • Database Version:9.5
  • Project Name:impact-app

Hi @nishant_khandelwal,
Welcome to the Forest Admin community!

I am afraid I can’t find an “impact-node” project (with agent version 2.16.9) having several users using it.
Are you sure this is the right project name? Do you share a single account to all your operational team?

It looks to be a configuration issue of your Admin backend configuration indeed.
If it was working before, did you recently change something that could explain the situation?

Thanks for your help!

@arnaud sorry I put different project name. I have corrected the name.
Project name : impact-app
Also, I didn’t change anything except minor UI-configurations in the last couple of months.
Earlier it was happening with my one teammate but now it’s happening with me as well

Thanks @nishant_khandelwal,

I tried a POST request to the endpoint and it returned a 504 (Gateway Time-out).
It is obviously a problem, can you dig into this error in your admin API servers configuration and try to solve it?

Thanks @arnaud for quick help.
It was not the forest specific problem. We recently reduced the timeout in load balancer that’s why I faced this issue.