# Error: Unprocessable Entity

**URL:** <https://community.forestadmin.com/t/error-unprocessable-entity/364>\
**Category:** Help me!\
**Created:** [May 30, 2020, 1:33pm UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364 "2020-05-30T13:33:13Z")\
**Posts on this page:** 18\
**Page:** 2

<div class="post-metadata">

**Author:** ![John](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/john/32/272_2.png) [@John](https://community.forestadmin.com/u/John)\
**Post date:** [June 1, 2020, 4:41pm UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/22 "2020-06-01T16:41:18Z")

</div>

> [@anon36130554](#):
>
> The docker command you are trying to run is used to generate an entire code base **localy** , which you already did.

Could I deploy UI (Frontend) locally, not in your servers? Nicolas saying about

> accessing our frontend directly on this machine

but I don’t understand what he talking about. Locally I can’t access anything but index page of Node Backend Server.

> [@anon36130554](#):
>
> If you want to deploy to a remote

No, I want to make local deployment, but what’s the point if I cannot do anything with it without your remote UI? If I trying to enter in local projects in cloud UI, it says that it cannot get access to localhost. But I haven’t other UI.

---

<div class="post-metadata">

**Author:** ![John](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/john/32/272_2.png) [@John](https://community.forestadmin.com/u/John)\
**Post date:** [June 1, 2020, 5:21pm UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/23 "2020-06-01T17:21:18Z")

</div>

If I understood correctly, UI absolutely unworkable without user-hosted backend, generated by lumber, and wrapped on SSL certs. I think you should create Docker image with completely workest example with Nginx and generated certificates (via certbot, for example).

Because when I, newbie, come to Forest Admin, I take your out-of-the-box deployments, with expectation to see how it works, without deep diving into. But it turns out that your “out-of-the-box” deployment is semi-workable - you need to wrap up Node with Nginx, or modify nodejs to install SSL-certs (and lumber and docs contains no word about this). Not all people every day installing nginx with SSL, and this “requirement” gonna be very annoying to their.

If I am wrong - let me know.

---

<div class="post-metadata">

**Author:** ![Arnaud\_Moncel](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/arnaud_moncel/32/24_2.png) [@Arnaud\_Moncel](https://community.forestadmin.com/u/Arnaud_Moncel)\
**Post date:** [June 2, 2020, 9:55am UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/24 "2020-06-02T09:55:06Z")

</div>

Hi @John 👋  
That’s not totally correct.

As stated on the website, Forestadmin only provide the UI & the UI API in order to make your lumber generated backend work. The architecture of the solution assure that your data remains in your database.  
The onboarding pages gives you all the needed commands to make it run on your local machine, assuming that port 3310 is available and database is accessible through the given database parameters.

The forest admin UI cannot work without a user-hosted backend, but it could totally be hosted locally and is able to request on `localhost` URL.

SSL/nginx/etc issues only appear when dealing with a remote/production environment (Localhost/127.0.0.1 should not cause any issues), since it is now a standard “webapp” requirement to run online apps with HTTPS.

In fact, since you provided your credential in the previous posts, I’m totally able to run a complete install on my local machine by just:

- Filling the database screen with your database connection parameters
- Running without any modifications the commands provided by the UI

If you encounter any errors related to this process, let us know. We are all here to help you through this 🙂

---

<div class="post-metadata">

**Author:** ![John](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/john/32/272_2.png) [@John](https://community.forestadmin.com/u/John)\
**Post date:** [June 2, 2020, 11:17am UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/25 "2020-06-02T11:17:56Z")

</div>

@Arnaud_Moncel, hi 👋! Thanks for your reply 😃

> [@Arnaud\_Moncel](#):
>
> The forest admin UI cannot work without a user-hosted backend, but it could totally be hosted locally and is able to request on `localhost` URL.

Please, explain me, how I can deploy UI on local? I couldn’t find any info about UI local deploying in google and your docs! It seems like no one in the world know how to use Forest Admin locally!

I’ve deployed locally DB, Backend (by lumber) on 3310. Now I want to deploy Forest UI to use it locally.

---

<div class="post-metadata">

**Author:** ![Arnaud\_Moncel](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/arnaud_moncel/32/24_2.png) [@Arnaud\_Moncel](https://community.forestadmin.com/u/Arnaud_Moncel)\
**Post date:** [June 2, 2020, 1:42pm UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/26 "2020-06-02T13:42:33Z")

</div>

You can’t/don’t have to deploy The forest UI locally, that’s the whole point of the architecture. Just connect to [https://app.forestadmin.com](https://app.forestadmin.com/), select your project, and you should be good to go.  
In our architecture, we are responsible for hosting the forestadmin UI (Accessible through [https://app.forestadmin.com](https://app.forestadmin.com/)). The UI connect to our API (For UI infos, stored in our end, like column visibility, charts positions, …) and your Admin API (generated by lumber) using a dynamic CORS mechanic.

The full onboarding steps should be:

- Before using forest, ensure that you have a DB that allow connection. Also ensure that port 3310 is available.
- Go to [http://app.forestadmin.com/new-project](http://app.forestadmin.com/new-project), then enter your project name
- Fill the database parameters page with your database infos (Even if your database is hosted locally), then next
- Run exactly the command given by the npm/docker process of your choice. When your lumber generated project is running locally (After npm/yarn start), [https://app.forestadmin.com](https://app.forestadmin.com/) should detect that your installation is running.

If everything goes fine:

- You should have a locally deployed admin-backend
- [https://app.forestadmin.com](https://app.forestadmin.com/) should be able to communicate with it, even on `localhost`

If not, you will probably have a stacktrace to share. That way, it’ll be easier for us to assist you.

---

<div class="post-metadata">

**Author:** ![rap2h](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/rap2h/32/25_2.png) [@rap2h](https://community.forestadmin.com/u/rap2h)\
**Post date:** [June 4, 2020, 3:08pm UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/28 "2020-06-04T15:08:39Z")

</div>

Hi @John ,

Could you check [this answer](https://community.forestadmin.com/t/waiting-for-your-backend-to-run/264/6)?

> 👉 When creating a development environment, host have to be explicitly `localhost` and be accessible via `http`. This is the only host Forest Admin allows without having to set 🔒 `https` , for security reasons; in a regular process, your development environment have to be local and accessible through `localhost`. Then, after this local environment works, you would be able to create other environments (_prodution_, _staging_, etc.). But still they will require to be accessible through 🔒 `https` only.

In other words, you can have only use `http://localhost:3310` but not `http://84.201.173.76:3310` (without a `s`). If you follow exactly the steps provided by @Arnaud_Moncel, I guess your backend should be accessible via `http://localhost:3310` . This step is important:

> Run exactly the command given by the npm/docker process of your choice. When your lumber generated project is running locally (After npm/yarn start), [https://app.forestadmin.com](https://app.forestadmin.com/) should detect that your installation is running.

After this step your backend should be accessible via `http://localhost:3310` **on your actual local computer** and display this:

 ![Capture d’écran 2020-06-04 à 17.08.17](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/1X/2733c762aabbd9b94492e132c680c69df255ca13.png)

---

<div class="post-metadata">

**Author:** ![John](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/john/32/272_2.png) [@John](https://community.forestadmin.com/u/John)\
**Post date:** [June 4, 2020, 3:23pm UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/29 "2020-06-04T15:23:44Z")

</div>

Yes, backend available from localhost. I’ve checked it by `curl http://localhost:3310/`

---

<div class="post-metadata">

**Author:** ![rap2h](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/rap2h/32/25_2.png) [@rap2h](https://community.forestadmin.com/u/rap2h)\
**Post date:** [June 4, 2020, 3:33pm UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/30 "2020-06-04T15:33:28Z")

</div>

Thank you.

I’m not sure to understand what you did. Do you mean you checked on your local computer that it’s accessible thorugh `http://localhost:3310` in your local computer browser?

You mentioned [http://84.201.173.76:3310/](http://84.201.173.76:3310/) in your previous message.

> Forest Backend is available on [http://84.201.173.76:3310/](http://84.201.173.76:3310/)

Is 84.201.173.76 a public address of your local computer? (i.e the one that you use to send the messages to this community). Could you confirm that (without using `curl`) you can access with your browser `http://localhost:3310` (not using the distant IP, but explicitly `localhost`). I must be sure about that before investigating.

---

<div class="post-metadata">

**Author:** ![John](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/john/32/272_2.png) [@John](https://community.forestadmin.com/u/John)\
**Post date:** [June 4, 2020, 3:49pm UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/31 "2020-06-04T15:49:49Z")

</div>

Lets forget about 84.201.173.76 (jopas\_remote) for a minute. I deployed it on a local machine just now. I successfully completed project creation step. But I cannot enter the project:  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/1X/3edbf29556c88955d3880e69002c9fb5b50e04c7.png)

This is jopas\_local.

---

<div class="post-metadata">

**Author:** ![John](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/john/32/272_2.png) [@John](https://community.forestadmin.com/u/John)\
**Post date:** [June 4, 2020, 3:54pm UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/32 "2020-06-04T15:54:13Z")

</div>

Eventually, I successfully deployed on local machine. Now I gonna try to do it on remote machine

---

<div class="post-metadata">

**Author:** ![John](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/john/32/272_2.png) [@John](https://community.forestadmin.com/u/John)\
**Post date:** [June 4, 2020, 4:02pm UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/33 "2020-06-04T16:02:40Z")

</div>

I successfully passed creation step (I think trouble was on your side. May be a little server lag), but I got an issue when trying to enter the project jopas\_remote2:  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/1X/b7379df8d588fda56a4977257e96b10b3134567c.png)

I strictly following an instruction of project creation. I’ve tried two times (jopas\_remote and jopas\_remote2) with the same result 🤷‍♀️

---

<div class="post-metadata">

**Author:** ![anon36130554](https://avatars.discourse-cdn.com/v4/letter/a/b3f665/32.png) [@anon36130554](https://community.forestadmin.com/u/anon36130554)\
**Post date:** [June 5, 2020, 7:10am UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/34 "2020-06-05T07:10:48Z")

</div>

Hello @John 👋

May I ask you the 6 last digits of the `env_secret` you are using for your project `jopas_remote2` please ?

Thanks in advance ✋

---

<div class="post-metadata">

**Author:** ![John](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/john/32/272_2.png) [@John](https://community.forestadmin.com/u/John)\
**Post date:** [June 5, 2020, 7:25am UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/35 "2020-06-05T07:25:29Z")

</div>

Hi 👋

`8e37dd`

…

---

<div class="post-metadata">

**Author:** ![anon36130554](https://avatars.discourse-cdn.com/v4/letter/a/b3f665/32.png) [@anon36130554](https://community.forestadmin.com/u/anon36130554)\
**Post date:** [June 5, 2020, 8:15am UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/36 "2020-06-05T08:15:55Z")

</div>

Thanks @John 👍

The environment secret is correct, but !

I’ve seen that you are currently running three different projects (one local, two name with `remote`).

If I understand what you are trying to achieve, you would like to have your project accessible remotely, which is fine but here is the recommended procedure for this.

You successfully passed the first step, which is create a project on your local environment 🎉 You should now use this one and use the feature: `deploy to a remote`. (go to your project settings, environments, you should see a button to deploy you project).

 ![Screenshot 2020-06-05 at 10.14.15](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/1X/8dbf2ef106edd2ae6819bad3ebe48b2ce1ccde98.png)  
Select `Deploy to a remote first`.

You will guided by the UI on how to do it, just follow the steps, you will be given some new environment variables to use (a new environment secret for instance) in your remote instance.

Tell me if it helps 🙌

---

<div class="post-metadata">

**Author:** ![John](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/john/32/272_2.png) [@John](https://community.forestadmin.com/u/John)\
**Post date:** [June 5, 2020, 8:27am UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/37 "2020-06-05T08:27:19Z")

</div>

Thx. But how I can solve the local deployment issue? I can’t enter the project at all ☹

---

<div class="post-metadata">

**Author:** ![anon36130554](https://avatars.discourse-cdn.com/v4/letter/a/b3f665/32.png) [@anon36130554](https://community.forestadmin.com/u/anon36130554)\
**Post date:** [June 5, 2020, 8:30am UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/38 "2020-06-05T08:30:23Z")

</div>

> [@John](#):
>
> Eventually, I successfully deployed on local machine. Now I gonna try to do it on remote machine

I thought you successfully created on a local machine.

What’s the error you are encountering please ?

---

<div class="post-metadata">

**Author:** ![John](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/john/32/272_2.png) [@John](https://community.forestadmin.com/u/John)\
**Post date:** [June 5, 2020, 8:33am UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/39 "2020-06-05T08:33:49Z")

</div>

I getting the next pop-up when trying to click on project jopas\_remote2 in UI:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/1X/7f24447dcbdc2126751040e54f2bac6a8e8f29b7.png)

[http://84.201.173.76:3310/](http://84.201.173.76:3310/)

---

<div class="post-metadata">

**Author:** ![anon37102731](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@anon37102731](https://community.forestadmin.com/u/anon37102731)\
**Post date:** [June 8, 2020, 3:15pm UTC](https://community.forestadmin.com/t/error-unprocessable-entity/364/41 "2020-06-08T15:15:43Z")

</div>

Hi @John,

Thanks a lot for your patience, we’ll do our best to help you being all set up with all your environments.

As stated here, there seems to be a mismatch between the expected `FOREST_ENV_SECRET` key for your jopas\_remote2 environment and the one available in the environment variables of the server hosting the lumber project.

You’ll need to go to the environment variables of the server hosting the lumber instance of your jopas\_remote2 environment and replace it by the one you’ll find on your settings (project settings \> environments).

![Screenshot 2020-06-08 at 17.13.44](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/1X/74867633f943794a225d02ada9535e1f3ef66798.png)

Once that is done, you should be able to access your jopas\_remote2 environment

I hope it helps

[Previous page](https://community.forestadmin.com/t/error-unprocessable-entity/364.md?page=1)
