Azure前门一直在路线一直到一个起源

发布于 2025-02-14 00:41:52 字数 231 浏览 0 评论 0原文

我们有一个azure前门,有两个起源。

但是这里的问题是第二个问题存在一些问题,应用程序未能启动,

因此我们通过前部起点组将其禁用,当我们撞到前门时,该应用程序显示该应用程序未能启动错误,而不是转到其他正在工作的来源。

然后,我们停止了第二个应用程序服务,并试图撞到前门,然后我们获得了错误403的错误 - 该网络应用程序停止了

它告诉S的数据仍将进入第二个。 如果有人面对同样的问题,请让我

We have a Azure Front Door which has two origins .

But the problem here is the 2nd one has some issues , the application failed to start

so we disabled it through front origin group and when we hit the front door it shows the app failed to start error instead of going to other origin which is working.

Then we stopped the app service for 2nd one and tried to hit the front door then we get the error for Error 403 - This web app is stopped

what it tells s its still going to 2nd one .
Please let me if anybody faces the same issue

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

小嗷兮 2025-02-21 00:41:52

错误403-此Web应用程序已停止

  1. 如果您的开放式公共API受到Azure App Service的公开访问,则该错误可能会导致此错误可能导致此错误。您使用用于访问应用程序服务的应用程序的IP地址未列出或呼叫可能会阻止。

    • 按照官方文档在门户网站中检查您的访问限制规则

转到Azure Portal - > app->网络 - >访问限制 - >配置访问限制

“在此处输入图像说明”

  • 尝试添加0.0.0.0.0.0/0并授予访问访问权限每个人。稍后,根据您的需求,您可以施加限制。如果您在授权呼叫之前接到禁止电话,则可能会产生效果。

“在此处输入映像说明”

  1. 前门考虑了后端池中的所有后端,即使健康探索了任何一个人,它们失败了,流量在所有方面均匀分布。请参阅

    • 默认情况下检查您的优先级, 前门仅将流量发送到最高优先级后端
    • 检查您的参数使用默认值 重量为50
    • 尝试将两个后端放在同一后端池中,这两个都应该是可用的,然后您可以停止一个后端。选择具有最小延迟范围的后端。 默认设置延迟敏感性属性为0,这意味着该请求将始终转发到最快的后端。

3.尝试禁用emforcecercertificatectificatenamecheck 来自Azure门户,并在添加到Orgin时检查您是否启用cerficate主题名称验证必须是 启用 这个问题。

4.试图通过此 azure前门路由不工作 gitaranisharmsft-4262

学分 前门#先决条件“ rel =” nofollow noreferrer“> https://learn.microsoft.com/en-us/azure/frontdoor/quickstart-create-front-door#prerequisites

https://learn.microsoft.com/en-us/azure/frontdoor/routing-methods

The Error 403 - This web app is stopped

  1. This error may cause If your open public API is restricted from public access on Azure App Service. Your application's IP address that you are using to access the app service is not whitelisted or calls may be blocking.

Go to azure portal -> app -> Networking ->Access Restriction -> Configure Access Restrictions

enter image description here

  • Try adding 0.0.0.0/0 and granting access to everyone. Later, based on your needs, you can impose limits. It could have an effect if you receive banned calls before authorized calls.

enter image description here

  1. Front Door considers all backends in a backend pool to be healthy even if health probes for any one of them fail, and traffic is distributed evenly across them all. Please refer Health probes

    • Check your Priority By default, Front Door sends traffic only to the top priority backends
    • Check your parameter uses a default weight of 50
    • Try to put two backends in the same backend pool both should be availability then you can stop one backend. Choose backends with a range of least latency. The latency sensitivity property is by default set to 0, which means that the request will always be forwarded to the fastest backend.

3.Try to disable EnforceCertificateNameCheck from the Azure portal and while adding to Orgin check whether you are enable Cerficate subject name validation must be enable for Troubleshooting this issue.

4.Try to add virtual directory /path in your app service by this Azure front Door routing not working throws error credits by GitaraniSharmaMSFT-4262

For your Reference :

https://learn.microsoft.com/en-us/azure/frontdoor/quickstart-create-front-door#prerequisites

https://learn.microsoft.com/en-us/azure/frontdoor/routing-methods

愁以何悠 2025-02-21 00:41:52

我们关联了现有的Orgin组。
创建了一个新的Orignin组,并更新并开始再次工作。
假设是由于某种原因,ORGHOUP被破坏了

we un associated the existing orgin-group.
Created a new orignin-group and updated and started working again.
Assumption is the orgingroup got corrupted due to some reason

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文