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

"Not Found" #219

Open
nick-pateman-avalara opened this issue Jul 25, 2019 · 1 comment
Open

"Not Found" #219

nick-pateman-avalara opened this issue Jul 25, 2019 · 1 comment

Comments

@nick-pateman-avalara
Copy link

Issue summary

After starting kong-dashboard and navigating to "http://localhost:8080", I receieve just "Not Found" message.

Your environment

  • Kong version = 1.2.1
  • Kong Dashboard version = 3.6.0 (Kong Dashboard versions before 3.0.0 aren't supported anymore)
  • Node version = 10.16.0
  • Npm version = 6.9.0

Issue description

After starting kong-dashboard, and navigating to the URL, I receive only "Not Found" in plain text.

As I am attempting to connect to the kong-api in my kubernetes cluster, this is exposed on https, but with a self-signed certificate, so I had to add the following 2 lines of code before the connection request in kong-dashboard.js

//these following 2 lines were added prior to the "connecting message"
terminal.info("Disabling dodgy SSL cert rejection.");
process.env["NODE_TLS_REJECT_UNAUTHORIZED"] = 0;

terminal.info("Connecting to Kong on " + argv.kongUrl + " ...");

Current behavior

kong-dashboard starts with the following output messages,

S C:\Source\Misc\kong-dashboard> npm start -- --kong-url https://172.18.84.203:32432

> [email protected] start C:\Source\Misc\kong-dashboard
> node ./bin/kong-dashboard start "--kong-url" "https://172.18.84.203:32432"

Disabling dodgy SSL cert rejection.
Connecting to Kong on https://172.18.84.203:32432 ...
Connected to Kong on https://172.18.84.203:32432.
Kong version is 1.2.1
Starting Kong Dashboard on port 8080
Kong Dashboard has started on port 8080

when I navigate to the url I get "Not Found" in plain text.

image

Expected behavior

Presumably I should see the dashboard?

Steps to reproduce

  1. Install kong into local kubernetes cluster (such as minikube)

  2. Run kong-dashboard with additional NODE_TLS_REJECT_UNAUTHORIZED = 0 setting

  3. Navigate to http://localhost:8080/

  4. Observe "Not Found" response

  5. Navigate to kong API using browser

  6. Allow self-signed certificate

  7. View JSON output from kong API

image

@kalion
Copy link

kalion commented Sep 28, 2019

You should do npm run build first

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

2 participants