Webserver URL returns blank page for airflow standalone for 3.0.0rc1

[dheerajturaga]

Apache Airflow version

3.0.0

If "Other Airflow 2 version" selected, which one?

No response

What happened?

Airflow URL returns blank page when running airflow standalone with 3.0.0rc1

What fails:

docker run -d -p 8080:8080 --name airflow_container apache/airflow:3.0.0.rc1.post4 airflow standalone

What passes:

docker run -d -p 8080:8080 --name airflow_container apache/airflow:2.10.5 airflow standalone

What you think should happen instead?

No response

How to reproduce

docker run -d -p 8080:8080 --name airflow_container apache/airflow:3.0.0.rc1.post4 airflow standalone

Then open the browser http://0.0.0.0:8080

Operating System

Ubuntu 24.04

Versions of Apache Airflow Providers

No response

Deployment

Other Docker-based deployment

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[tirkarthi]

Are you seeing any errors in the browser console as the page is empty?

[tirkarthi]

Looks like a CORS issue on loading the assets with 0.0.0.0 resolving to 127.0.0.1 . Can you please try http://localhost:8080 ?

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8080/static/assets/index-D7eB8u6o.js. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200.

[jscheffl]

I can confirm - http://127.0.0.1:8080 is not working (CORS) but http://localhost:8080 works.

[dheerajturaga]

I can confirm aswell. It would be great if this could be addressed

[Dev-iL]

I'd say this is a pretty serious limitation: I'm running docker on one machine and connecting to it from another, so I have no choice but using the hostname in the address.

When connecting using the hostname, there's no CORS, but the browser is attempting to retrieve resources from (its) localhost, on which there's no webserver running.

[ashb]

We should change the default BASE_URL to be empty, and then pick the current base default based on the current request.host etc I think.

That will mean it works out of the box for Direct and breeze without needing extra changes.

[pierrejeambrun]

CORS settings can be controlled from the config by:

• api.access_control_allow_headers
• api.access_control_allow_methods
• api.access_control_allow_origins

By default no origin is allowed, meaning that only the same origin is accepted by the browser.