My Azure search service was working perfectly until two weeks ago when I had an error message saying "An existing connection was forcibly closed by the remote host". I tried to update the nuget packges to use the latest versions, I refreshed the tokens but nothing works. Any help please, my site is completely down because of this.
Asked
Active
Viewed 105 times
0
-
are you using free tier? – Thiago Custodio Apr 21 '20 at 01:32
-
Yes I'm using free tier and it has been working fine for more than 4 years – user5373892 Apr 21 '20 at 06:23
-
there's a new behavior for free tier. If it won't receive requests in 90 days, it will delete your resource. That may be the problem. – Thiago Custodio Apr 21 '20 at 13:58
-
Yeah I'm aware of the new thing regarding the free tier but my API is get queries everyday so it shouldn't be that problem – user5373892 Apr 22 '20 at 18:28
-
The service is still up and running, azure support checked the status and told me that there is nothing wrong but I still can't search – user5373892 Apr 22 '20 at 18:29
1 Answers
1
Have you checked to see whether these issues are relating to SSL handshake negotiation? If your client isn't using TLS 1.2, that's the first place I would suggest looking.
Steve Maine
- 91
- 2
-
Shouldn't the SDK use the appropriate SSL handshake? If not how can I specify it manually please? – user5373892 Apr 21 '20 at 12:40