I took the liberty to anonymise your post, be careful not to share sensitive information on public forums
Give me some time to look at your problem and get back to you !
Ok it seems to be because your endpoint (APPLICATION_HOST) is not set as https, see this part of the documentation to read about setting up forest on a remote environment with docker @John
The ssl needs to be enabled on your server, redirect the traffic through the port 443 with ssl enabled.
Do you still have the same error after enabling ssl on your server ?
Are you talking about Forest Admin Backend Server? lumber-forestadmin relies on Node Server. I haven’t another servers. I’m looking for opportunity to set ssl certificates via lumber-cli.
Forest’s frontend require your lumber project to be accessible via https, the lumber project is connected to your database (which is on the same server from what I see, so no need for ssl here) and it is not connected to your own backend.
What FA does is generate a backend to connect with FA’s frontend which give you an admin panel that you can customize following your needs.
Right, lumber-cli does generate backend, which based on Node’s web-server on 80 port, and Forest cannot establish connection with https protocol of this web-server because your Node’s app.js haven’t configured any SSL to fit this requirement.
And now I see I need to deploy my own server to install SSL-certs for Forest Backend, or I need to make modifications in app.js. But I don’t see how I can just install certs without this dances to Node’s web-server.
Node.js doesn’t necessary need an https configuration, you can use a reverse proxy to route the request through https.
For exemple you can look at this thread.
I am ready to deploy it locally, but I do not understand how to use Forest Frontend in this case. Frontend need public-hosted backend to access. All of my services deployed locally and all the troubles because Forest Frontend cannot work without cloud
I’ll try to be more clear
FA’s goal is to allow you to quickly setup an admin panel, to this end we scan your db and we generate a lumber project for you.
The error you are getting appears when you try to generate your lumber project.
We advise to first generate a development environment locally and then deploy it to a remote server for your production environment.
Remote environments needs to work through https to enforce security.
Local environment doesn’t need to since they run on your machine and you are accessing our frontend directly on this machine (the request are done on localhost).
Forest frontend is just the interface with whom your generated project communicates.
The lumber project is the “bridge” between forest and your database, where you put your logic.
Your own app (back and front) are not connected to FA, only your database.
Don’t hesitate if I explained badly I advise you to read the doc, it’s explained more clearly than what I can do here.
How I can directly access Forest Frontend - locally, without remotes? I could not find any way but Frontend on Forest servers. I don’t know how to use Forest without your servers.
In this message, I’ll assume that you are deploying to a remote (I’ve seen that you already own two development environments, and that one remote environment is awaiting to be configured).
The docker command you are trying to run is used to generate an entire code base localy, which you already did. So there, you are trying to re-create an additional code base which is not what you want.
If you want to deploy to a remote, you just have to follow the wizard steps by going to your project settings --> environment --> deploy button --> deploy to a remote first
You will see that no docker command is needed. This is because we recommend to version the generated code you’ve got from the first docker command you ran, then deploy it (upload it) to your remote instance.
From there, you will need to edit your environment variables (in the .env file) as your DB endpoint might have changed for example. And additionally, you will need to activate SSL in your remote instance for security reasons. The SSL has nothing to do with Forest, Lumber or either the DB. It has to be configured on your remote machine to establish a secure connexion between forest UI and you project (if you can give us your provider name, we might help with some documentation on how to do that).
If I misunderstood your problem at some point, please correct me and we will iterate