Bug Report: Vtadmin page does not show any data on first install in version 19 about vitess

[frouioui]

To add to this issue, when reproducing the steps in the consol we can see that API requests are blocked by CORS as seen in the log below (visible in the web consol). This issue happens even though we use the URL printed by the 101 script and also when going on localhost. The --http-origin flag on the vtadmin-api side seems to be set correctly according to the log, however in the request header when calling the API the field Origin is set to localhost (instead of http://Florents-MacBook-Pro-2.local in my case).

Access to fetch at 'http://florents-macbook-pro-2.local:14200/api/vtctlds' from origin 'http://florents-macbook-pro-2.local:14201' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

[notfelineit]

Thanks @frouioui ! Would you mind sharing where you see the Origin being set, and the network request if you have it available? 🙏

[notfelineit]

Ok, I was able to recreate on my new m2 laptop 😄 Might have something to do with capitalization:

snippet from my startup script:

vtadmin-api expects vtadmin-web at, and set http-origin to "http://Francess-MacBook-Pro.local:14201"
vtadmin-api is running!
  - API: http://Francess-MacBook-Pro.local:14200
  - Logs: /Users/francesthai/planetscale/vitess/examples/local/vtdataroot/tmp/vtadmin-api.out
  - PID: 13404

Building vtadmin-web...
~/planetscale/vitess ~/planetscale/vitess/examples/local
~/planetscale/vitess/examples/local

Installing nvm...

nvm is already installed!

Configuring Node.js 20.12.2

v20.12.2 is already installed.
Now using node v20.12.2 (npm v10.7.0)

Setting VITE_VTADMIN_API_ADDRESS to "http://Francess-MacBook-Pro.local:14200"

[notfelineit]

Good news is that after normalizing the hostnames in the start up scripts, this works fine now:

from #15839

[notfelineit]

This should be fixed now that #15839 is merged. It's backported to 19 and 18 as well. Please let us know if you run into anymore issues @bantyK

[bantyK]

I am sorry folks, but still the same issue. I took the latest pull on main for version 19 and ran the 101_initial_cluster script.

[notfelineit]

@bantyK can you share your output from running ./101_initial_cluster.sh as well as the request body of one of those CORS errors in your network tab?

[bantyK]

hi @notfelineit I had to do a fresh install and now its working. Thank you for fixing this. :)

[notfelineit]

@bantyK yay that's great! 🥳