WCF Exception Could not find a base address that matches scheme http for the endpoint

Question

I m trying to host a WCF web service on a separate Website in IIS with https at 443 as the only binding    The following configurations works well when I use it in a website which uses both the bindings  http 80    https 443    If I remove the http binding  it starts throwing the following error   Could not find a base address that matches scheme http for the endpoint with binding BasicHttpBinding  Registered base address schemes are  https    How do I make it work in an IIS website with https binding only      lt system serviceModel gt       lt bindings gt         lt basicHttpBinding gt           lt binding name  defaultBasicHttpBinding  gt             lt security mode  Transport  gt               lt transport clientCredentialType  None  proxyCredentialType  None  realm     gt               lt message clientCredentialType  Certificate  algorithmSuite  Default    gt             lt  security gt           lt  binding gt         lt  basicHttpBinding gt       lt  bindings gt       lt client gt         lt endpoint address  http   localhost ERPService retailPayment svc                  binding  basicHttpBinding  bindingConfiguration  defaultBasicHttpBinding                  contract  RetailPaymentService RetailPayment SVRetailPaymentService  name  EnterpriseRetailPayment    gt       lt  client gt       lt behaviors gt         lt serviceBehaviors gt           lt behavior name  MyServiceTypeBehaviors  gt             lt serviceMetadata httpGetEnabled  true    gt             lt serviceDebug includeExceptionDetailInFaults  true    gt           lt  behavior gt           lt behavior gt             lt serviceMetadata httpGetEnabled  true    gt             lt serviceDebug includeExceptionDetailInFaults  true    gt           lt  behavior gt         lt  serviceBehaviors gt         lt endpointBehaviors gt           lt behavior name  MyEndPointBehavior  gt             lt  -- lt SchemaValidator enabled  true   gt -- gt           lt  behavior gt         lt  endpointBehaviors gt       lt  behaviors gt       lt services gt         lt service name  SettlementSalesCollection SaleItemService  behaviorConfiguration  MyServiceTypeBehaviors  gt           lt endpoint behaviorConfiguration  MyEndPointBehavior  binding  basicHttpBinding                    name  SettlementSalesCollection                    contract  SettlementSalesCollection CITransactionSettlementListenerService    gt           lt endpoint name  mexEndpoint  contract  IMetadataExchange  binding  mexHttpBinding  address  mex    gt         lt  service gt       lt  services gt       lt extensions gt         lt behaviorExtensions gt           lt add name  SchemaValidator               type  SettlementSalesCollection SchemaValidation SchemaValidationBehavior CustomBehaviorSection  SettlementSalesCollectionService  Version 1 0 0 0  Culture neutral    gt         lt  behaviorExtensions gt       lt  extensions gt       lt protocolMapping gt         lt add binding  basicHttpsBinding  scheme  https    gt       lt  protocolMapping gt       lt serviceHostingEnvironment aspNetCompatibilityEnabled  true  multipleSiteBindingsEnabled  true    gt     lt  system serviceModel gt

User · Accepted Answer

Your configuration should look similar to that. You may have to change <transport clientCredentialType="None" proxyCredentialType="None" /> depending on your needs for authentication. The config below doesn't require any authentication.

<bindings>
    <basicHttpBinding>
        <binding name="basicHttpBindingConfiguration">
            <security mode="Transport">
                <transport clientCredentialType="None" proxyCredentialType="None" />
            </security>
        </binding>       
    </basicHttpBinding>
</bindings>

<services>
    <service name="XXX">
        <endpoint
            name="AAA"
            address=""
            binding="basicHttpBinding"
            bindingConfiguration="basicHttpBindingConfiguration"
            contract="YourContract" />
    </service>
<services>

That will allow a WCF service with basicHttpBinding to use HTTPS.

User · Answer

I tried the binding according to the answer by  Szymon but It did not work for me  I tried basicHttpsBinding which is new in  net 4 5 and It solved the issue  Here is the complete configuration that works for me     lt system serviceModel gt       lt serviceHostingEnvironment aspNetCompatibilityEnabled  true  multipleSiteBindingsEnabled  false    gt       lt behaviors gt         lt serviceBehaviors gt           lt behavior gt             lt serviceMetadata httpGetEnabled  false  httpsGetEnabled  true   gt             lt serviceDebug includeExceptionDetailInFaults  true   gt           lt  behavior gt         lt  serviceBehaviors gt       lt  behaviors gt       lt bindings gt         lt basicHttpsBinding gt           lt binding name  basicHttpsBindingForYourService  gt             lt security mode  Transport  gt               lt transport clientCredentialType  None  proxyCredentialType  None   gt             lt  security gt           lt  binding gt         lt  basicHttpsBinding gt       lt  bindings gt       lt services gt         lt service name  YourServiceName  gt           lt endpoint address    binding  basicHttpsBinding  bindingName  basicHttpsBindingForYourService  contract  YourContract    gt         lt  service gt       lt  services gt      lt  system serviceModel gt    FYI  My application s target framework is 4 5 1  IIS web site that I created to deploy this wcf service only has https binding enabled

User · Answer

You can get this if you ONLY configure https as a site binding inside IIS    You need to add http 80  as well as https 443  - at least I did  -

User · Answer

My issue was caused by missing bindings in IIS  in the left tree view  Connections   under Sites  Right click on your site   edit bindings   add   https  Choose  IIS Express Development Certificate  and set port to 443 Then I added another binding to the webconfig    lt endpoint address  wsHttps  binding  wsHttpBinding  bindingConfiguration  DefaultWsHttpBinding  name  Your bindingname  contract  Your contract     gt   Also added to serviceBehaviours    lt serviceMetadata httpGetEnabled  false  httpsGetEnabled  true    gt   And eventually it worked  none of the solutions I checked on stackoverflow for this error was applicable to my specific scenario  so including here in case it helps others

User · Answer

Open IIS And right click on Default App Pool and Add Binding to make application work with HTTPS protocol   type   https  IP address   All unassigned  port no   443  SSL Certificate   WMSVC  then  Click on and restart IIS  Done

User · Answer

In my case this fixed the issue   Go to Project Properties by clicking F4 on the project name Set SSLEnabled   true    Project Properties Image

User · Answer

In my case the binding name in under protocol mapping did not match the binding name on the endpoint  They match in the example below    lt endpoint address    binding  basicHttpsBinding  contract  serviceName    gt    and       lt protocolMapping gt           lt add binding  basicHttpsBinding  scheme  https    gt       lt  protocolMapping gt

User · Answer

My issue was also caused by missing https binding in IIS   Selected default website   On the far right pane selected Bindings   add   https  Choose  IIS Express Development Certificate  and set port to 443

[c#] WCF Exception: Could not find a base address that matches scheme http for the endpoint

Examples related to c#

Examples related to wcf

Examples related to web-services