Skip to content
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

Getting "Cannot GET /" when visiting localhost:8080 #30

Closed
mitchellfranklin opened this issue Mar 9, 2016 · 5 comments
Closed

Getting "Cannot GET /" when visiting localhost:8080 #30

mitchellfranklin opened this issue Mar 9, 2016 · 5 comments

Comments

@mitchellfranklin
Copy link

Hi All,

I have successfully installed Kong-Dashboard however when I go to http://localhost:8080 the screen returned is Cannot GET /.

any assistance would be greatly appreciated.

Thanks

Mitch

@gajen0981
Copy link

I am getting the same error on RHEL 7 environment.
Here is the npm-debug.log

[root@apimgmt1 kong-dashboard]# cat npm-debug.log 0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/bin/npm', 'start' ] 2 info using npm@2.14.12 3 info using node@v4.3.2 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info prestart kong-dashboard@1.1.0 6 info start kong-dashboard@1.1.0 7 verbose unsafe-perm in lifecycle true 8 info kong-dashboard@1.1.0 Failed to exec start script 9 verbose stack Error: kong-dashboard@1.1.0 start:node ./bin/kong-dashboard start 9 verbose stack Exit status 1 9 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:214:16) 9 verbose stack at emitTwo (events.js:87:13) 9 verbose stack at EventEmitter.emit (events.js:172:7) 9 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:24:14) 9 verbose stack at emitTwo (events.js:87:13) 9 verbose stack at ChildProcess.emit (events.js:172:7) 9 verbose stack at maybeClose (internal/child_process.js:821:16) 9 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) 10 verbose pkgid kong-dashboard@1.1.0 11 verbose cwd /home/sunthara/kong-dashboard 12 error Linux 3.10.0-327.4.5.el7.x86_64 13 error argv "/usr/bin/node" "/bin/npm" "start" 14 error node v4.3.2 15 error npm v2.14.12 16 error code ELIFECYCLE 17 error kong-dashboard@1.1.0 start:node ./bin/kong-dashboard start 17 error Exit status 1 18 error Failed at the kong-dashboard@1.1.0 start script 'node ./bin/kong-dashboard start'. 18 error This is most likely a problem with the kong-dashboard package, 18 error not with npm itself. 18 error Tell the author that this fails on your system: 18 error node ./bin/kong-dashboard start 18 error You can get their info via: 18 error npm owner ls kong-dashboard 18 error There is likely additional logging output above. 19 verbose exit [ 1, true ]

@gajen0981
Copy link

Found the issue and it's not with the code and it's because of directory permissions and didn't properly install the bower requirements.

This worked:

git clone https://github.com/PGBI/kong-dashboard.git
cd kong-dashboard
bower update
npm install
npm start

@haikuo81
Copy link

I am also get "Cannot GET /", @gajen0981, could you please tell me which directory should give correct permissions?

@nimboya
Copy link

nimboya commented Jul 21, 2016

Thank you @gajen0981 What you said worked had to update the bower and do npm install to compile the assets. But still could not access the APIs already created previously.

Also if you use Ubuntu ensure you install the node-legacy for it to some npm commands. And ensure you allow all permission on the folder so as to allow creation of files and folders easily

So in my case i had to do this:

git clone https://github.com/PGBI/kong-dashboard.git
sudo chmod -R 777 kong-dashboard
cd kong-dashboard
npm install
bower update
npm install
npm start

@PGBI
Copy link
Owner

PGBI commented Dec 15, 2017

This was caused by an error at build time. Closing as npm package for Kong-Dashboard is now shipped pre-built.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants