---

This section details on the original issue you should resolve

<issue_title>[BUG] UI not working on plain HTTP</issue_title>
<issue_description>### MLflow version

3.8.0

System information

• OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 24.04.1
• Python version: 3.12.3
• yarn version, if running the dev UI: N/A

Describe the problem

We are running an MLflow tracking server & UI on an internal VPN (Tailscale) and have so far been using plain HTTP to access the UI since the server is not exposed to the internet and it's simpler than generating certificates etc.

We recently switched to 3.8.0, and the UI stopped working (blank page). The tracking is still working fine, as is the Python client. This prompted me to look into the dev console, where the following JavaScript error appears:

Uncaught TypeError: crypto.randomUUID is not a function

As far as I understand, this is due to modern browsers only providing that function on HTTPS connections (or on connections to localhost). In Chrome I can manually override this to whitelist our internal domain names, but Safari has no such option as far as I can tell.

Steps to reproduce the bug

Start version 3.8.0 of MLflow, and access the UI on an HTTP connection on a host other than localhost in Safari or Chrome (maybe other browsers as well).

Code to generate data required to reproduce the bug

No response

Is the console panel in DevTools showing errors relevant to the bug?

[Error] TypeError: crypto.randomUUID is not a function. (In 'crypto.randomUUID()', 'crypto.randomUUID' is undefined)
	getInstallationId (main.bbdf6ce4.js:2:346113)
	(anonymous function) (main.bbdf6ce4.js:2:345974)
	26595 (main.bbdf6ce4.js:2:345908)
	n (main.bbdf6ce4.js:2:2657701)
	80739 (main.bbdf6ce4.js:2:2011865)
	n (main.bbdf6ce4.js:2:2657701)
	(anonymous function) (main.bbdf6ce4.js:2:2695653)
	(anonymous function) (main.bbdf6ce4.js:2:2703789)
	Global Code (main.bbdf6ce4.js:2:2703792)

Does the network panel in DevTools contain failed requests relevant to the bug?

No network errors</issue_description>

Comments on the Issue (you are @copilot in this section)

@WeichenXu123 You are right, `crypto.randomUUID()` is part of the **Web Crypto API** , it is only available in **HTTPS** or **http://localhost**

As of now, native MLflow server uses http,

I think you can configure a Reverse proxy on the same machine (e.g., Nginx in front for HTTPS), then the request flow is like

client HTTPS -> nginx :443 -> the MLFlow server http://127.0.0.1:5000

There are many guides on web, e.g. : https://www.scaleway.com/en/docs/tutorials/nginx-reverse-proxy/</comment_new>
<comment_new>@WeichenXu123
on the other hand, configuring Reverse proxy for HTTPS is a complicated task for end-users, is it possible to add fallback code in MLflow front-end in the case of http://non-localhost-address ? @BenWilson2 @daniellok-db </comment_new>
<comment_new>@WeichenXu123
I think we can replace crypto.randomUUID with code like

import { v4 as uuidv4 } from 'uuid';
uuidv4();

it works with HTTP.

assuming we just use the uuid as session id / installation id etc, "secure random generator" is not required, the node.js uuid package is enough. </comment_new>
<comment_new>@WeichenXu123
#19573 is a good start,

but I suggest to avoid implementing uuid by ourself, but calling uuid library:

import { v4 as uuidv4 } from 'uuid';

uuidv4();