GitHub部署后显示503网站正在建设中 [英] 503 Site Under Construbtion after GitHub deployment shows Success

问题描述

在Azure Web App的两个部署插槽上进行连续部署大约两年以来，我遇到了零问题.突然，(意味着太平洋时间2019年2月10日晚上11点)，其中一个部署导致显示503服务器错误，同时显示成功". (有效)"在部署中心下.日志也没有显示错误.我尝试过重新同步，断开连接并重新连接存储库.我什至尝试使用另一个分支，结果始终是503.

I have had zero issues with continuous deployment for about two years now on two deployment slots for an Azure Web App. Suddenly, (meaning 11PM Pacific time on Feb 10, 2019) one of the deployments results in a 503 server error while showing "Success (Active)" under the Deployment Center. The logs also show no errors. I have tried resyncing, disconnecting and reconnecting the repo. I have even tried using another branch, and the result is always a 503.

我的其他Web应用程序插槽设置没有此问题.两者都是同一App Service上的插槽，并且日志显示的结果完全相同.我不知为何要弄清楚为什么一个插槽可以工作，而同一应用程序服务上的另一个插槽却不能工作.

My other Web app slot setup doesn't have this problem. Both are slots on the same App Service and the logs show the exact same results. I'm at a loss for figuring out why one slot would work but another slot on the same App Service wouldn't work.

还有其他类似的经历吗?

Anyone else have a similar experience?

推荐答案

Thanks for reporting the issue! Just to clarify, do you recall making any specific changes prior to this issue? On which region have you provisioned your app?

1.请检查一下App Service诊断程序是否提供了任何指针，从而减少了尝试和出错的机会，并通过建议潜在的解决方案加快问题解决的速度.

1.Kindly check to see if App Service diagnostics provides any pointers, it reduces the chance of trial and error and expedites problem resolution by recommending potential solutions.

要访问App Service诊断，请在 中导航到您的App Service应用程序 Azure 门户 .在左侧导航栏中，点击诊断并解决问题.

To access App Service diagnostics, navigate to your App Service app in the Azure portal. In the left navigation, click on Diagnose and solve problems.

2.您还可以查看服务运行状况通知.

2.You could also review the Service Health notifications.

服务健康"- 服务 问题视图显示Azure服务中任何正在影响您资源的持续问题.您可以了解问题何时开始以及哪些服务和区域受到影响.您还可以阅读最新更新以了解Azure在做什么 解决问题.请参见

The ‘Service Health’ -Service issues view shows any ongoing problems in Azure services that are impacting your resources. You can understand when the issue began, and what services and regions are impacted. You can also read the most recent update to understand what Azure is doing to resolve the issue. See, Azure Service Health

如果问题仍然存在， 可以共享您的WebApp名称 直接在此处或

If the issue still persists, could you share your WebApp name directly here or indirectly?

这篇关于GitHub部署后显示503网站正在建设中的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！