tag:support.appharbor.com,2010-11-23:/discussions/problems/89609-wcf-no-protocol-binding-matches-the-given-addressAppHarbor: Discussion 2018-10-19T03:07:21Ztag:support.appharbor.com,2010-11-23:Comment/418841062017-02-03T22:41:33Z2017-02-03T22:41:33ZWCF - No protocol binding matches the given address<div><p>Hi!<br>
I fix this problem added to the web.config file.<br>
Close de issue.<br>
Thanks.</p></div>nschmidttag:support.appharbor.com,2010-11-23:Comment/418841062017-02-03T22:43:50Z2017-02-03T22:43:50ZWCF - No protocol binding matches the given address<div><p>Hi,</p>
<p>Was just about to follow up on this, but glad to hear you
figured it out already! Let me know if there's anything else I can
help with.</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/418841062017-02-03T23:02:06Z2017-02-03T23:02:06ZWCF - No protocol binding matches the given address<div><p>Ok!<br>
Now I'm getting this: The message with Action '' cannot be
processed at the receiver, due to a ContractFilter mismatch at the
EndpointDispatcher. This may be because of either a contract
mismatch (mismatched Actions between sender and receiver) or a
binding/security mismatch between the sender and the receiver.
Check that sender and receiver have the same contract and the same
binding (including security requirements, e.g. Message, Transport,
None).</p>
<p>Any idea?<br>
Thanks!</p></div>nschmidttag:support.appharbor.com,2010-11-23:Comment/418841062017-02-07T02:09:34Z2017-02-07T02:09:34ZWCF - No protocol binding matches the given address<div><p>Hi,</p>
<p>Can you point me to an URL where this error is returned so I can
take a closer look (as it doesn't seem to apply to the endpoints I
just tested)?</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/418841062017-02-07T22:22:55Z2017-02-07T22:22:55ZWCF - No protocol binding matches the given address<div><p>Hi Rune!<br>
Good news! I fix it... it was a config.</p>
<p>Thanks!</p></div>nschmidt