I have a windows server 2008 which I had deployed my website that accesses clients API just fine, due to end of support of Server 2008, we have formatted it to Server 2016 and re-deployed all applications, it was all was running fine until a user tried to access on of our client's API and cannot connect. We can successfully connect to the API when on debug/dev mode, but when accessing through our deployed website, we always encounter error saying "here was no endpoint listening at https://someurl?wsdl that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details". Im lost.
I already tried installing all IIS Features and backward compatibility, still nothing,
Here is my config for binding.
<binding name="IPRNImplPortBinding1" closeTimeout="00:01:00" openTimeout="00:01:00"
receiveTimeout="00:10:00" sendTimeout="00:01:00" allowCookies="false"
bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"
maxBufferPoolSize="524288" maxBufferSize="65536" maxReceivedMessageSize="65536"
textEncoding="utf-8" transferMode="Buffered" useDefaultWebProxy="true"
messageEncoding="Text">
<readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
maxBytesPerRead="4096" maxNameTableCharCount="16384" />
<security mode="Transport">
<transport clientCredentialType="None" proxyCredentialType="None"
realm="" />
<message clientCredentialType="Certificate" algorithmSuite="Default" />
</security>
</binding>
Don't know if this will help anyone but what solve the problem is adding the hostname of the webservice/api I was trying to connect on the HOST file located at C:\Windows\System32\drivers\etc of the server. I'm not familiar with the host file but it really works like a charm.