Localhost environment not loading

Expected behavior

Use a “Localhost” environment when having a server at localhost:3001

Actual behavior

The Localhost environment stuck at the loading icon. The localhost:3001 server never gets any request.

Failure Logs


This just started recently, probably today.

  • Package Version: “forest-express-sequelize”: “^6.3.13”,
  • Express Version: 4.17.1
  • Sequelize Version: 5.22.3
  • Database Dialect: Postgres
  • Database Version: Postgres 10.7
  • Project Name: fm-admin

If I’m not mistaken, this seems to be a larger - platform wide - issue? I’m just getting started with ForestAdmin and have been wracking my brain trying to figure out what I’m doing wrong. Looks like it wasn’t me. Hope it’s being looked into

Hi @weiwei9, @conrad,

A regression has been introduced today about protocol redirection.

As a workaround, if your environment has a HTTP localhost endpoint, can you try to reach you admin panel using http://app.forestadmin.com (instead of https://app.forestadmin.com).

Let us know if it works.

Seeing the same behavior. Also, filters are not working in Chrome on MacOS. Not sure about other browsers/environments.

Unfortunately, this does not seem to fix the issue. I’m specifically working locally and neither http or https seem to be working for me. Can I provide any other information that would help you troubleshoot?

Hopefully this helps?

1 Like



Hello @conrad @Jack_Roberts @weiwei9,

Both issue (localhost & filters not working) are currently in the process of beeing rollbacked right now and everything should come back to normal soon.

Really sorry about the inconvenience, but your feedback really helped us find the issue here, thanks :pray:

1 Like

Meanwhile we fix the issue, you can replace your dev environment settings (in project settings):

  • from: http://localhost:3310
  • to:

We will keep you updated once we fix the issue for localhost configuration

1 Like

Awesome! Thanks for the heads up and for working diligently to get it cleared up :slight_smile: Glad to have been able to help!

Hi @weiwei9, @conrad, @Jack_Roberts, @jonl,

The patch has been released 9 hours ago, everything should be fine since.
Let us know if the issue is not solved on your end.