Oops, cannot reach your application. Are you sure it is running? about lumber

[kaleb]

Same issue. This is what I get when I run curl -I http://localhost:3002/forest:

HTTP/1.1 204 No Content
X-Powered-By: Express
Vary: Origin
Access-Control-Allow-Credentials: true
Date: Tue, 18 Jun 2019 22:17:33 GMT
Connection: keep-alive

[jcoulaud]

Sorry for the output, yes it was running but I was on the wrong server when I executed the command.
Here it is :
$ curl -I http://localhost:3000/forest
HTTP/1.1 204 No Content X-Powered-By: Express Date: Fri, 18 Nov 2016 20:00:53 GMT Connection: keep-alive

[SeyZ]

Hey @jcoulaud Can you run a curl in your terminal and show me the output?
$ curl -I http://localhost:3000/forest

Thanks!

[jcoulaud]

curl: (7) Failed to connect to localhost port 3000: Connection refused

[SeyZ]

Hey @jcoulaud So it means your server is not running :( Did you run the node ./bin/www in your folder?

[jcoulaud]

But still the same message when I'm on the UI Interface :/

[jcoulaud]

Hi ! Any news :) ?

[SeyZ]

Hey @jcoulaud ! Sorry about the delay

So you're server is running but the browser can't make requests to it. Do you have errors on your Chrome console?

[jcoulaud]

Hey !
So when I try to login on the UI interface (http://app.forestadmin.com/****/login), I have this message in the center top
Login Oops, cannot reach your application. Are you sure it is running? If your application is running, you might have a CORS configuration issue.

And in the console
OPTIONS http://localhost:3000/forest/sessions net::ERR_CONNECTION_REFUSED

And my server :
node ./bin/www 🌳 Open your admin UI: http://app.forestadmin.com 🌳

[SeyZ]

Ok it seems to be a CORS issue. Normally, your microservice injects the right CORS headers in the http request but it does not seems to work with yours.

Do you have the cors middleware there?
https://github.com/ForestAdmin/lumber/blob/master/templates/app/app.js#L21

[jcoulaud]

Yes I have it

[jcoulaud]

Hi there !
I would like to give it a shot again, so can you help me please :) ?
Do you have any idea what's could cause the CORS issue ?
Best

[SeyZ]

Hey @jcoulaud can you drop me an email ([email protected]) to schedule a quick call to help us figure out what happens with your CORS problem ?

[permpkin]

I have the same issue, when asked for the password it spits out "http://localhost:3000/forest/sessions net::ERR_CONNECTION_REFUSED" in the console. Is this supposed to be setup locally? I had set it up on a VPS?

[SeyZ]

@permpkin it's suppose to work with a localhost URL without any problem. We can investigate more your issue in details if you drop me an email [email protected] ;)

[ap1969]

Hi,
Is there any solution to this?I'm getting the exact same issue:curl responds with 204 code, ERR_CONNECTION_REFUSED in console.

Regards,
Andy

[permpkin]

@Notifium It seems to be ( as Seyz mentioned ) designed to work with "localhost" ( rather than on a remote VPS ). Try setting it up on your local machine ( That's how I resolved the ERR's ).

[adrianricardo]

any update here? I'm getting the same error on localhost. Production works just fine

[samshinde]

Does any one came across below issue
node ./bin/www
🌳 Open your admin UI: http://app.forestadmin.com 🌳
[forest] 🌳🌳🌳
VError: IP Whitelist error: Forest server request error: Not Found
at /home/amol/other-projects/amol/sampleserve/sample/node_modules/forest-express/dist/services/ip-whitelist.js:25:21
at tryCatcher (/home/amol/other-projects/amol/sampleserve/sample/node_modules/forest-express/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/home/amol/other-projects/amol/sampleserve/sample/node_modules/forest-express/node_modules/bluebird/js/release/promise.js:503:31)
at Promise._settlePromise (/home/amol/other-projects/amol/sampleserve/sample/node_modules/forest-express/node_modules/bluebird/js/release/promise.js:560:18)
at Promise._settlePromise0 (/home/amol/other-projects/amol/sampleserve/sample/node_modules/forest-express/node_modules/bluebird/js/release/promise.js:605:10)
at Promise._settlePromises (/home/amol/other-projects/amol/sampleserve/sample/node_modules/forest-express/node_modules/bluebird/js/release/promise.js:680:18)
at Async._drainQueue (/home/amol/other-projects/amol/sampleserve/sample/node_modules/forest-express/node_modules/bluebird/js/release/async.js:126:16)
at Async._drainQueues (/home/amol/other-projects/amol/sampleserve/sample/node_modules/forest-express/node_modules/bluebird/js/release/async.js:136:10)
at Immediate.Async.drainQueues (/home/amol/other-projects/amol/sampleserve/sample/node_modules/forest-express/node_modules/bluebird/js/release/async.js:16:14)
at runCallback (timers.js:789:20)
at tryOnImmediate (timers.js:751:5)
at processImmediate [as _immediateCallback] (timers.js:722:5)
[forest] 🌳🌳🌳 Cannot find the project related to the envSecret you configured. Can you check on Forest that you copied it properly in the Forest initialization?

[samshinde]

My forest server was not running, now all things are going smoothly. 👍

[anilprasad]

I am getting the similar error as mentioned above
🌳 Open your admin UI: http://app.forestadmin.com 🌳
[forest] 🌳🌳🌳
VError: IP Whitelist error: Forest server request error: Not Found
...and the remaining part as mentioned by @samshinde

[jakebaird]

Hey guys, i've got the same issue

Oops, cannot reach your application. Are you sure it is running? If your application is running, you might have a CORS configuration issue.

I just setup an SSL certificate, would this have anything to do with it?

[seyhunak]

Any update of this? Forest requests get 204 response.

OPTIONS /forest/sessions 204 0.119 ms - 0
GET /forest/sessions 404 12.255 ms - 1425

[yid0]

Same issue for trying to unlock data ! is there any solution?
RequestURL: http://localhost:3000/forest/sessions
Response : Connection Refused

[manthis]

I'm having the exact same issue. Nothing in the logs of my application and my CORS policy has not changed but it stopped working suddenly. Don't know what's the problem here.

FYI here is the error I can find in the console:
Access to XMLHttpRequest at 'https://********/forest/sessions' from origin 'https://app.forestadmin.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.

[manthis]

Ok I solved the issue by adding this to my CORS configuration in Express:

`const app = express();

// We configure CORS
let corsOptions = {
    origin: '*',
    credentials: true,
};
app.use(cors(corsOptions));`

[unicolai42]

Same issue. This is what I get when I run curl -I http://localhost:3002/forest:

HTTP/1.1 204 No Content
X-Powered-By: Express
Vary: Origin
Access-Control-Allow-Credentials: true
Date: Tue, 18 Jun 2019 22:17:33 GMT
Connection: keep-alive

Try with an other port (For example 3003 rather than 3000). It works for me.

[navjinder]

Hi There

I am seeing the same issues [see image]

[serhanbalci]

Still not working.

[arnaudbesnier]

Hi @serhanbalci,

This error message can occur in various cases.
How did you validate that you server is running?
Can you also provide details about your issue?

Thanks for your help 🙏

[serhanbalci]

I solved in development mode, but there is no documentation for production. I did not find any useful piece of docs publish it for production. Is there any ? thanks

[promisepreston]

I put up an awesome Medium article here for anyone interested in integrating Forest Admin in a Rails Application:

https://medium.com/@promisepreston/up-and-running-with-forest-admin-in-rails-aa63599e9adc

Let me know if you find it helpful in any way.

[arnaudbesnier]

Hi guys, as mentioned in the past:

This error message can occur in various cases.
How did you validate that you server is running?

This message comes from an expected error.
It usually means that your admin backend server is not running or properly configured.

Let me close this issue, as there is no clear action to do here for the Forest Admin team.