<p>I installed airflow using Kubernetes and have login the airflow UI. It shows all dags, but they are not shown correctly.</p>
<p>1/ There is no on/off buttons on the left of Dag name, it just show empty checkbox.</p>
<p>2/ The &quot;Recent Tasks&quot; and &quot;DAG Runs&quot; columns look like they are trying to load something;</p>
<p>3/ If I click and therefore go to any of DAG, it looks like it tries to load something;</p>
<p>I tried both airflow 2.0.0 and 1.10.11 and they show the same so it is not because of version.</p>
<p>What is the problem of the airflow and how to fix that?</p>
<p><a href="https://i.stack.imgur.com/7mdLG.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/7mdLG.png" alt="enter image description here" /></a></p>
<p><a href="https://i.stack.imgur.com/h9Orn.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/h9Orn.png" alt="enter image description here" /></a></p>
<p>------- here I provide more information according to Ofek Hod's suggestion:
1/ run &quot;kubectl logs &lt;pod_id&gt; webserver&quot;, after I login airflow web UI, I got many http 404 response. e.g.
<a href="https://i.stack.imgur.com/erUuw.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/erUuw.png" alt="404 when login" /></a></p>
<p>after I click any dag in airflow WebUI I got some other 404 response
<a href="https://i.stack.imgur.com/4wFE2.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/4wFE2.png" alt="404 after I click dag" /></a></p>

user389955
<p>Airflow interprets all your .py files in your dags folder first, I guess something goes wrong there.<br />
<strong>As a rule-of-thumb, first access webserver and scheduler logs</strong> (for kub <code>kubectl logs</code>?), maybe you can find a hint there.</p>
<p>If not, try first to make a &quot;clean&quot; airflow instance without any of your dags code or related .py files- point the dags folder to an empty directory and see what happens (better if you turn on example dags configuration).</p>
<p>If that works, add your .py files from the original dag folder incrementally until you find problematic code.</p>
<p>If it's not working, probably the scheduler or webserver are messed up, please check the logs again with better attention.</p>
