Using the 9.1ML cluster atm but also tried the 7.3 and 8.1.

Databricks is deployed on google platform and I was using the trial.

It is quite difficult to debug if the spark ui is only semi accessible.

Part of the results in raw html are visible but all css, js assets as well as any details if I klick on jobs in the ui popup are blocked (403).

302 https://dp-....gcp.databricks.com/driver-proxy/o/.../1007-074754-weeps90/41616/jobs/job?id=4&csrf=3.....

403 https://dp-....gcp.databricks.com/driver-proxy/o/.../1007-074754-weeps90/48884/proxy/local-163474460...

403 https://dp-....gcp.databricks.com/driver-proxy/o/.../1007-074754-weeps90/48884/proxy/local-163474460...

(everything which is behind the reverseProxy /driver-proxy/o/.../1007-074754-weeps90/48884/)

The spark ui works if I terminate the cluster and check it in Cluster or notebook tab. Its the history server that works fine but the live access proxy does not. I assume there are some issues with oauth but I cannot find any logs to tell me where the 403 happens.