findItemsAdvanced Could not connect because it was rejected by the target computer.

[aibo.collections]

When I execute the following function, I get "The connection could not be made because it was rejected by the target computer: 209.140.129.41:80" and I cannot search for the item.
API: FindItemsAdvancedResponse
Function: findItemsAdvanced

InnerException {"The connection could not be made because it was rejected by the target computer. 66.211.163.3:80"} System.Exception {System.Net.Sockets.SocketException}
No endpoint was listening on ex http://svcs.ebay.com/services/search/FindingService/v1. This is typically caused by an incorrect address or SOAP action. See InnerException (if any) for more information."} System.Exception {System.ServiceModel.EndpointNotFoundException
InnerException {"The connection could not be made because it was rejected by the target computer. 66.211.163.3:80"} System.Exception {System.Net.Sockets.SocketException}

If you know how to solve this problem, please help me.

[shipscript]

@aibo.collections 

The endpoint protocol should be https.  

See if that change produces a better result.

[jdm.king]

Hello,
Thank you very much for your reply.

Changing the endpoint to https worked.

I would like to thank you for your answer.

[shipscript]

@aibo.collections 

You are very welcome. You may want to mark the answer so it has better visibility to others.

[amaurbli0]

Hi, changing to https did the trick for me, thanks!

Do you know by any chance why the http support suddenly dropped without notice?

Or maybe I missed the info?

In another thread (https://community.ebay.com/t5/Traditional-APIs-Search/My-FindItemsAdvanced-calls-started-return-erro...) other people mention http endpoint not working starting 1st June at midnight ...

[shipscript]

@amaurbli0 

This change was announced in 2019 to occur in 2020. I remember hustling to get my server updated and to modify all of my apps to meet that deadline. I'm surprised eBay allowed it to continue three years, so was somewhat surprised by the failures occurring this late in the game.  While the Finding API was switched to HTTPS, the Shopping API did not support HTTPS, so I had split protocols for little awhile.

https://developer.ebay.com/updates/blog/https-only-finding-api

Here is the letter I received 2020.02.27

Dear Developer,

You are receiving this email because our records indicate that you have an application that calls the eBay Finding API. As we communicated earlier this year, eBay is discontinuing support for the HTTP endpoints. We announced we were disabling the HTTP endpoints on March 31, 2020. Now, starting on March 31, 2020, the eBay Finding API will work over HTTPS only (e.g., https://svcs.ebay.com/services/search/FindingService/v1). Any requests submitted via HTTP will fail.

To optimize API performance over HTTPS, please configure your client to reuse TLS sessions. To help you adapt to HTTPS, we will post information about TLS session reuse for popular clients. Please monitor the Finding API Discontinuing Support for HTTP developer blog post for details and updates.

[amaurbli0]

Oh, ok I get it now why I didn't get the info, I started to use the Finding API about a year ago.

Yeah, weird that they kept supporting HTTP for that long after the deadline they announced, but well, this had to happen a day or another.

Thanks for the info!