Hello outerbounds, I am trying to setup metaflow UI on my local setup and I don't know what to do, as the connection between metaflow services and metaflow UI fails without explicit error message. Can you guide me towards fixing this problem, please ? I am running metaflow services on localhost:8084 with "python3 -m services.metadata_service.server" (docker compose up was failing due to a missing relation public.flowsv3" something like that) and I am running the metaflow UI with " docker run -p 3000:3000 -e METAFLOW_SERVICE=http://localhost:8084/ metaflow-ui:latest". Both are running, I can see the metaflow UI in my browser. The only thing is that it displays "Error loading data", 500, Unknown error. On the service side, it seems like it received the request but could not answer it : "INFOaiohttp.access127.0.0.1 [11/Sep/20231000:14 +0000] "GET /ws HTTP/1.1" 404 173 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36"".

I would try METAFLOW_SERVICE=http://localhost:3000/api , but before that I recommend making sure metaflow service works as expected with no errors, and Metaflow can talk to it. I.e. you have METAFLOW_DEFAULT_METADATA=service in your metaflow config,

METAFLOW_SERVICE_URL

set to service url, and when you run flows, they work fine and get nice integer-looking run ids

Hello, thank you for your help. So I tried what you said and it did not solve my problem yet, but at least I was able to check that metaflow services seems to work. I ran my flow with METAFLOW_SERVICE_URL=http://localhost:8084 METAFLOW_DEFAULT_METADATA="service" and on the metaflow-service side I was receiving lots of GET/POST requests with status 200 so it seems to work. I also checked that I had good looking run IDs.

hmm kind of depends on the setup, but high level there are 3 components: UI "static" files, js/css etc., metadata service, metadata UI backend. UI front end talks to metadata UI backend. Here's the diagram how its deployed on AWS. Ignore load balancer stuff since you're doing it locally:

"i think you may be missing UI backend" that is what I was going to say, as when I tried to launch the container of metaflow service the backend failed to launch. Oh I see ! thank you I did not see this command ! I will try it, thank you