[Bug] Can't get server running from source.
See original GitHub issueBug Report
- Version of Majestic: 1.3.0
- Version of Jest: 20.0.3
- Version of Node: 8.15.1
- Operating System: macOS Mojave
I am trying to help contribute by fixing one of the issues I created (#120). However when trying to start the server through VS Code, I get this error:

I tried also running from CLI with yarn prod
and it closes without an error just warnings.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
How To Deal With A Server Not Found Message?
To fix the server-cannot-be-found message on your computer, check your connectivity first (wi-fi, router, etc.) and the URL being entered in the ...
Read more >How to the Fix "DNS Server Not Responding" Error - Kinsta®
The "DNS Server Not Responding" message tells you your computer isn't able to connect to the internet. Learn why it happens and how...
Read more >HTTP 500 Internal Server Error: What It Means & How to Fix It
You'll see the HyperText Transfer Protocol (HTTP) 500 Internal Server Error when your server issue doesn't fit another error code.
Read more >Error 120 - Unable to connect to server - Source Elements
Error 120 indicates that Source-Connect is not able to communicate with the Source Elements server and cannot retrieve settings from source-elements.com:80.
Read more >How To Troubleshoot Common Site Issues on a Linux Server
Before blindly trying to track down a problem, try to check the logs of your web server and any related components. These will...
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 Free
Top 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
Using port 9000 fixes the issue after adding jest to the node_modules
I commented that line and also got Cannot GET / now. The same issue as @dangus21. I have merged your recent changes into my fork as well and still get the error.