CODEWITHSUNDEEP
c#azureazure-web-app-servicebotframework
Sanpas
Sanpas

Reputation: 1180

Botframework Web Application Azure IDX20803: Unable to obtain configuration from: '[PII is hidden]

We have a issues with our bot

It was working fine during the last 4 months without any errors.

But today we receive the relevant error : 

2018-12-17T17:50:25  PID[5736] Error       
Error refreshing OpenId configuration: System.InvalidOperationException: 
    IDX20803: Unable to obtain configuration from: '[PII is hidden]'. 
            ---> System.IO.IOException: IDX20804: Unable to retrieve document from: '[PII is hidden]'. 
            ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. 
            ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. 
            ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. 
            ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

The complete log file was shown at this link : https://pastebin.com/ZLx9G9W7

I think it's a exception due too IIS configuration but we have not changed anything on that.

Thanks you in advance.

Upvotes: 2

Views: 1886

Answers (2)

FireFlying
FireFlying

Reputation: 41

I know this post is quite old, but I just ran into this exact error message yesterday with an Azure App Service (Bot Framework v4.15):

Exception: System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'https://login.botframework.com/v1/.well-known/openidconfiguration'.

The issue was that the App Service had lost the ability to resolve DNS. This was confirmed by opening the Kudu Debug Console and running:

nameresolver.exe login.botframework.com (and any other hostname)

Unfortunately, this was a temporary outage of some sort on Microsoft's end (currently being investigated with MS support). I had to deploy a separate plan and App Service in order to restore service. Frustratingly, the broken App Service started magically working again the next morning.

Upvotes: 0

Arnold Pistorius
Arnold Pistorius

Reputation: 532

Okay I have had a phone call with an engineer from Microsoft. They told me BotFramework doesn't support TLS 1.0 anymore and we have to migrate to version 1.2. They have anounced this in a blog post: https://blog.botframework.com/2018/11/06/announcement-azure-bot-service-enforcing-transport-layer-security-tls-1-2/

My bot was fixed by adding this line in the startup code (in my case it was Application_Start in Global.asax.cs):

System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;

Upvotes: 4

Related Questions