PGBI/kong-dashboard

"Not Found"

nick-pateman-avalara opened this issue · 1 comments

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

> kong-dashboard@3.6.0 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

You should do npm run build first