Oops, cannot reach your application. Are you sure it is running?
See original GitHub issueHi, First of all, great job guys 😃
Little problem here. I got the following message when I try to login in the admin UI:
Login
Oops, cannot reach your application. Are you sure it is running?
even though I’m sure it’s running on my server. Tested it on Chrome and Safari.
Best, julien
Issue Analytics
- State:
- Created 7 years ago
- Comments:33 (8 by maintainers)
Top Results From Across the Web
How do I resolve an Entity ID error or the error "Oops! We ...
While configuring or logging in to an application with Duo Access Gateway (DAG), you might see "Oops! We could not authenticate you to...
Read more >Fix Hmm We Can't Reach This Page Error in Microsoft Edge
How to solve the “Hmm, we can't reach this page” problem in Microsoft Edge.A number of users have reported this strange issue relevant...
Read more >How to Solve UCPath "Oops" Google Chrome Login Error
Retry the UCPath application by manually entering the URL (example: ucpath.universityofcalifornia.edu) into the web browser or using your browser history ...
Read more >5 Ways to Fix the “Can't Reach This Page” Error on Microsoft ...
Here are five ways to fix the “Can't Reach This Page” error in Microsoft Edge, in case you ever experience the error on...
Read more >I get the error "Oops, something went wrong" when trying to ...
Your Chrome Browser is Blocking Third-Party Cookies · Using Multiple Google Accounts · Clear Browser Cache and Cookies ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Same issue. This is what I get when I run
curl -I http://localhost:3002/forest
: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