If restart_airflow.sh completed successfully but the UI is still not loading, try these troubleshooting steps:
Check for HTTPS redirect: Browsers often force https:// automatically. Make sure the URL in your address bar starts with http:// and not https://. Try opening the link in an Incognito/Private window or using a different browser.
Wait for initialization: The script prints “Service is healthy” as soon as Docker starts, but the Airflow webserver container needs another 2 to 3 minutes to run database migrations and fully boot. Wait a bit and refresh.
Network/VPN blocks: If you are on a corporate network or VPN, access to port 8080 might be blocked. Try disconnecting from your VPN or loading the link on your mobile phone using cellular data.
Check container status: If it still won’t load, a container might have crashed (often due to a syntax error in your DAG). Run this in your CloudShell to inspect the containers:
export airflow_instance_id=$(aws ec2 describe-instances --filters 'Name=tag:Name,Values=de-c2w4lab1-airflow-instance' --query "Reservations[].Instances[].InstanceId" --output text)
aws ssm send-command --instance-ids $airflow_instance_id --document-name "AWS-RunShellScript" --parameters commands=["sudo docker ps -a"] --query "Command.CommandId" --output text
Take the Command ID printed from the step above and run this to see the logs (replace <COMMAND_ID>):
aws ssm get-command-invocation --command-id <COMMAND_ID> --instance-id $airflow_instance_id --query "StandardOutputContent" --output text
Check if the airflow-webserver container is Up or if it has Exited.