Under which category would you file this issue?
Airflow Core
Apache Airflow version
3.1.6
What happened and how to reproduce it?
On Debian VM, Airflow 3.1.5 installed by pip.
When I upgrade to 3.1.6 with pip install, the install is successful but after restarting airflow-api-server.service the web ui is blank.
If I inspect the source code in my webbrowser I've :
<!doctype html>
<html style="height: 100%" dir="ltr" lang="en">
<head>
<meta charset="UTF-8" />
<base href="[/](view-source:https://51.15.230.10/)" />
<link rel="icon" type="image/png" href="./static/pin_32.png" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Airflow</title>
<script type="module" crossorigin src="./static/assets/index-BpILZJIF.js"></script>
</head>
<body style="height: 100%">
<div id="root" style="height: 100%"></div>
</body>
</html>The airflow-api-server.service status give me : "GET /static/assets/index-BpILZJIF.js HTTP/1.1" 404 Not Found
sudo systemctl status airflow-api-server.service
● airflow-api-server.service - Airflow api-server daemon
Loaded: loaded (/etc/systemd/system/airflow-api-server.service; enabled; preset: enabled)
Active: active (running) since Wed 2026-04-15 17:29:14 CEST; 12min ago
Main PID: 12401 (airflow api_ser)
Tasks: 7 (limit: 14334)
Memory: 180.7M
CPU: 5.728s
CGroup: /system.slice/airflow-api-server.service
└─12401 "airflow api_server -- host:0.0.0.0 port:8080"
avril 15 17:29:19 scw-pedantic-ardinghelli bash[12401]: INFO: Started server process [12401]
avril 15 17:29:19 scw-pedantic-ardinghelli bash[12401]: INFO: Waiting for application startup.
avril 15 17:29:19 scw-pedantic-ardinghelli bash[12401]: INFO: Application startup complete.
avril 15 17:29:19 scw-pedantic-ardinghelli bash[12401]: INFO: Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
avril 15 17:29:19 scw-pedantic-ardinghelli bash[12401]: INFO: 127.0.0.1:59952 - "GET / HTTP/1.1" 200 OK
avril 15 17:29:33 scw-pedantic-ardinghelli bash[12401]: INFO: 127.0.0.1:60230 - "GET / HTTP/1.1" 200 OK
avril 15 17:29:33 scw-pedantic-ardinghelli bash[12401]: INFO: 127.0.0.1:60242 - "GET /static/assets/index-BpILZJIF.js HTTP/1.1" 404 Not Found
avril 15 17:29:33 scw-pedantic-ardinghelli bash[12401]: INFO: 127.0.0.1:60246 - "GET /static/pin_32.png HTTP/1.1" 404 Not Found
avril 15 17:34:35 scw-pedantic-ardinghelli bash[12401]: INFO: 127.0.0.1:38148 - "GET / HTTP/1.1" 200 OK
avril 15 17:34:35 scw-pedantic-ardinghelli bash[12401]: INFO: 127.0.0.1:38158 - "GET /static/assets/index-BpILZJIF.js HTTP/1.1" 404 Not Found
If I check if this script exists :
sudo find /opt/airflow/ -type f -name index-BpILZJIF.js
/opt/airflow/env/lib/python3.11/site-packages/airflow/ui/dist/assets/index-BpILZJIF.js
What you think should happen instead?
No response
Operating System
Debian 12 / Python 3.11.2
Deployment
Virtualenv installation
Apache Airflow Provider(s)
No response
Versions of Apache Airflow Providers
apache-airflow-providers-amazon==9.19.0
apache-airflow-providers-common-compat==1.11.0
apache-airflow-providers-common-io==1.7.0
apache-airflow-providers-common-sql==1.30.2
apache-airflow-providers-fab==2.4.0
apache-airflow-providers-http==5.6.2
apache-airflow-providers-mongo==5.3.1
apache-airflow-providers-postgres==6.5.1
apache-airflow-providers-smtp==2.4.1
apache-airflow-providers-ssh==4.2.1
apache-airflow-providers-standard==1.10.2
Official Helm Chart version
Not Applicable
Kubernetes Version
No response
Helm Chart configuration
No response
Docker Image customizations
Not Applicable
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
Under which category would you file this issue?
Airflow Core
Apache Airflow version
3.1.6
What happened and how to reproduce it?
On Debian VM, Airflow 3.1.5 installed by pip.
When I upgrade to 3.1.6 with pip install, the install is successful but after restarting
airflow-api-server.servicethe web ui is blank.If I inspect the source code in my webbrowser I've :
The airflow-api-server.service status give me :
"GET /static/assets/index-BpILZJIF.js HTTP/1.1" 404 Not FoundIf I check if this script exists :
What you think should happen instead?
No response
Operating System
Debian 12 / Python 3.11.2
Deployment
Virtualenv installation
Apache Airflow Provider(s)
No response
Versions of Apache Airflow Providers
apache-airflow-providers-amazon==9.19.0
apache-airflow-providers-common-compat==1.11.0
apache-airflow-providers-common-io==1.7.0
apache-airflow-providers-common-sql==1.30.2
apache-airflow-providers-fab==2.4.0
apache-airflow-providers-http==5.6.2
apache-airflow-providers-mongo==5.3.1
apache-airflow-providers-postgres==6.5.1
apache-airflow-providers-smtp==2.4.1
apache-airflow-providers-ssh==4.2.1
apache-airflow-providers-standard==1.10.2
Official Helm Chart version
Not Applicable
Kubernetes Version
No response
Helm Chart configuration
No response
Docker Image customizations
Not Applicable
Anything else?
No response
Are you willing to submit PR?
Code of Conduct