HTTP 404 response for /dashboard http endpoint

[akira-kurogane]

What type of bug is this?

Unexpected error, User Experience

What subsystems are affected?

Standalone mode, Frontend

Minimal reproduce step

Start a standalone instance. Open http://<bind address>:4000/dashboard.

Same issure whether 127.0.0.1, 0.0.0.0, or external IP of host used.

What did you expect to see?

The dashboard. Or at least some HTML response.

What did you see instead?

Nothing, except the HTTP 404 reply headers.

Demonstrating using curl verbose header output:

$ curl -v http://127.0.0.1:4000/dashboard
*   Trying 127.0.0.1:4000...
* Connected to 127.0.0.1 (127.0.0.1) port 4000
* using HTTP/1.x
> GET /dashboard HTTP/1.1
> Host: 127.0.0.1:4000
> User-Agent: curl/8.10.1
> Accept: */*
> 
* Request completely sent off
< HTTP/1.1 404 Not Found
< content-length: 0
< date: Fri, 20 Sep 2024 06:22:43 GMT
< 
* Connection #0 to host 127.0.0.1 left intact

What operating system did you use?

Arch

What version of GreptimeDB did you use?

0.9.3

Relevant log output and stack trace

The full greptime log output during the HTTP request

2024-09-20T06:07:31.565513Z DEBUG hyper::proto::h1::io: parsed 3 headers
2024-09-20T06:07:31.565636Z DEBUG hyper::proto::h1::conn: incoming body is empty
2024-09-20T06:07:31.566042Z DEBUG request{method=GET uri=/dashboard version=HTTP/1.1}: tower_http::trace::on_request: started processing request
2024-09-20T06:07:31.566501Z DEBUG request{method=GET uri=/dashboard version=HTTP/1.1}: tower_http::trace::on_response: finished processing request latency=0 ms status=404
2024-09-20T06:07:31.566891Z DEBUG hyper::proto::h1::io: flushed 82 bytes
2024-09-20T06:07:31.567745Z DEBUG hyper::proto::h1::conn: read eof

[akira-kurogane]

Other services seem to be fine, fwiw. The postgres port at least works fine.

[MichaelScofield]

@akira-kurogane Are you running the GreptimeDB with our released binary, or compiled from the source code? If it's the latter one, please run cargo build with feature servers/dashboard.

[akira-kurogane]

That was it - I had built from source.

When I rebuilt with cargo build --features servers/dashboard the dashboard UI began to be served.