-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm start in server gives error #11
Comments
@React-Vishnu you are trying to run If you don't want to use https then remove |
Hi @sthnaqvi thank you for your response . And i tried with ssl certificate path as you mentioned and without using -S but all shows the same error. |
and i don't know it is needed or not but i have changed my apache2 default port to 8080, nginx default port to 80 location /explorer/app { |
s and 1 error generated. gypgyp ERR!ERR! stack Error: |
when i try run this package in my server it shows below error. can you please help me? i have tried with and without reverse proxy server but same result
fs.js:646
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
Error: ENOENT: no such file or directory, open 'key.pem'
at Object.fs.openSync (fs.js:646:18)
.
.
.
npm ERR! Linux 4.15.0-1037-aws
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start"
npm ERR! node v8.10.0
npm ERR! npm v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start:
http-webnode ./app -a localhost -p 8000 -c-1
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script 'http-webnode ./app -a localhost -p 8000 -c-1'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the eth-block-explorer package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! http-webnode ./app -a localhost -p 8000 -c-1
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs eth-block-explorer
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls eth-block-explorer
npm ERR! There is likely additional logging output above.
The text was updated successfully, but these errors were encountered: