https with WCF error Could not find base address that matches scheme https

Question

I go to https   mywebsite MyApp Myservice svc and get the following error    The link works if I use http        The service   MyApp MyService svc  cannot be activated due to an exception during compilation   The exception message is  Could not find a base address that matches scheme https for the endpoint with binding BasicHttpBinding  Registered base address schemes are  http      EDIT  So if I change address    to address  https         then I get this error instead    Error  The protocol  https  is not supported      The ChannelDispatcher at  https       Annotation svc  with contract s    Annotation   is unable to open its IChannelListener    Here s what my Web Config looks like    lt services gt         lt service behaviorConfiguration  AnnotationWCF AnnotationBehavior                name  AnnotationWCF Annotation  gt                 lt endpoint address    binding  basicHttpBinding  bindingConfiguration  BasicHttpBinding Annotation                        contract  AnnotationWCF Annotation    gt                 lt endpoint address                       binding  basicHttpBinding  bindingConfiguration  SecureTransport                    contract  AnnotationWCF Annotation    gt                 lt endpoint address  mex  binding  mexHttpBinding  contract  IMetadataExchange    gt         lt  service gt       lt bindings gt   lt basicHttpBinding gt       lt binding name  BasicHttpBinding Annotation  maxBufferSize  2147483647              maxReceivedMessageSize  2147483647  gt           lt readerQuotas maxDepth  2147483647  maxStringContentLength  2147483647              maxArrayLength  2147483647  maxBytesPerRead  2147483647              maxNameTableCharCount  2147483647    gt       lt  binding gt       lt binding name  SecureTransport  maxBufferSize  2147483647              maxReceivedMessageSize  2147483647  gt           lt security mode  Transport  gt           lt transport clientCredentialType  None   gt           lt  security gt           lt readerQuotas maxDepth  2147483647  maxStringContentLength  2147483647              maxArrayLength  2147483647  maxBytesPerRead  2147483647              maxNameTableCharCount  2147483647    gt       lt  binding gt   lt  basicHttpBinding gt

User · Answer

Make sure SSL is enabled for your server!

I got this error when trying to use a HTTPS configuration file on my local box which doesn't have that certificate. I was trying to do local testing - by converting some of the bindings from HTTPS to HTTP. I thought it would be easier to do this than try to install a self signed certificate for local testing.

Turned out I was getting this error becasue I didn't have SSL enabled on my local IIS even though I wasn't intending on actually using it.

There was something in the configuration for HTTPS. Creating a self signed cert in IIS7 allowed HTTP to then work :-)

User · Answer

I think you are trying to configure your service in a similar way to the following config  There is more information here  Specify a Service with Two Endpoints Using Different Binding Values  Also  other than for development  it s probably not a good idea to have both HTTP  amp  HTTPS endpoints to the same service  It kinda defeats the purpose of HTTPS  Hope this helps    lt service type  HelloWorld  IndigoConfig  Version 2 0 0 0  Culture neutral  PublicKeyToken null  gt       lt endpoint         address  http   computer 8080 Hello          contract  HelloWorld  IndigoConfig  Version 2 0 0 0  Culture neutral  PublicKeyToken null          binding  basicHttpBinding          bindingConfiguration  shortTimeout       lt  endpoint gt       lt endpoint         address  http   computer 8080 Hello          contract  HelloWorld  IndigoConfig  Version 2 0 0 0  Culture neutral  PublicKeyToken null          binding  basicHttpBinding          bindingConfiguration  Secure        lt  endpoint gt   lt  service gt   lt bindings gt       lt basicHttpBinding          name  shortTimeout          timeout  00 00 00 01          gt        lt basicHttpBinding          name  Secure  gt           lt Security mode  Transport    gt        lt  basicHttpBinding gt   lt  bindings gt

User · Answer

In my case i am setting security mode to  TransportCredentialOnly  instead of  Transport  in binding  Changing it resolved the issue   lt bindings gt     lt webHttpBinding gt       lt binding name  webHttpSecure  gt         lt security mode  Transport  gt           lt transport clientCredentialType  Windows   gt  lt  transport gt         lt  security gt         lt  binding gt     lt  webHttpBinding gt   lt  bindings gt

User · Answer

It turned out that my problem was that I was using a load balancer to handle the SSL  which then sent it over http to the actual server  which then complained   Description of a fix is here  http   blog hackedbrain com 2006 09 26 how-to-ssl-passthrough-with-wcf-or-transportwithmessagecredential-over-plain-http   Edit  I fixed my problem  which was slightly different  after talking to microsoft support   My silverlight app had its endpoint address in code going over https to the load balancer   The load balancer then changed the endpoint address to http and to point to the actual server that it was going to  So on each server s web config I added a listenUri for the endpoint that was http instead of https   lt endpoint address    listenUri  http    LOAD BALANCER ADDRESS         gt

User · Answer

I had this exact same problem   Except my solution was to add an  s  to the binding value   Old   binding  mexHttpBinding   New  binding  mexHttpsBinding   web config snippet    lt services gt       lt service behaviorConfiguration  ServiceBehavior  name  LIMS UI Web WCFServices Accessioning QuickDataEntryService  gt           lt endpoint behaviorConfiguration  AspNetAjaxBehavior  binding  webHttpBinding  bindingConfiguration  webBinding               contract  LIMS UI Web WCFServices Accessioning QuickDataEntryService    gt           lt endpoint address  mex  binding  mexHttpsBinding  contract  IMetadataExchange    gt       lt  service gt

User · Answer

I think you are trying to configure your service in a similar way to the following config  There is more information here  Specify a Service with Two Endpoints Using Different Binding Values  Also  other than for development  it s probably not a good idea to have both HTTP  amp  HTTPS endpoints to the same service  It kinda defeats the purpose of HTTPS  Hope this helps    lt service type  HelloWorld  IndigoConfig  Version 2 0 0 0  Culture neutral  PublicKeyToken null  gt       lt endpoint         address  http   computer 8080 Hello          contract  HelloWorld  IndigoConfig  Version 2 0 0 0  Culture neutral  PublicKeyToken null          binding  basicHttpBinding          bindingConfiguration  shortTimeout       lt  endpoint gt       lt endpoint         address  http   computer 8080 Hello          contract  HelloWorld  IndigoConfig  Version 2 0 0 0  Culture neutral  PublicKeyToken null          binding  basicHttpBinding          bindingConfiguration  Secure        lt  endpoint gt   lt  service gt   lt bindings gt       lt basicHttpBinding          name  shortTimeout          timeout  00 00 00 01          gt        lt basicHttpBinding          name  Secure  gt           lt Security mode  Transport    gt        lt  basicHttpBinding gt   lt  bindings gt

User · Answer

It turned out that my problem was that I was using a load balancer to handle the SSL  which then sent it over http to the actual server  which then complained   Description of a fix is here  http   blog hackedbrain com 2006 09 26 how-to-ssl-passthrough-with-wcf-or-transportwithmessagecredential-over-plain-http   Edit  I fixed my problem  which was slightly different  after talking to microsoft support   My silverlight app had its endpoint address in code going over https to the load balancer   The load balancer then changed the endpoint address to http and to point to the actual server that it was going to  So on each server s web config I added a listenUri for the endpoint that was http instead of https   lt endpoint address    listenUri  http    LOAD BALANCER ADDRESS         gt

User · Answer

I think you are trying to configure your service in a similar way to the following config  There is more information here  Specify a Service with Two Endpoints Using Different Binding Values  Also  other than for development  it s probably not a good idea to have both HTTP  amp  HTTPS endpoints to the same service  It kinda defeats the purpose of HTTPS  Hope this helps    lt service type  HelloWorld  IndigoConfig  Version 2 0 0 0  Culture neutral  PublicKeyToken null  gt       lt endpoint         address  http   computer 8080 Hello          contract  HelloWorld  IndigoConfig  Version 2 0 0 0  Culture neutral  PublicKeyToken null          binding  basicHttpBinding          bindingConfiguration  shortTimeout       lt  endpoint gt       lt endpoint         address  http   computer 8080 Hello          contract  HelloWorld  IndigoConfig  Version 2 0 0 0  Culture neutral  PublicKeyToken null          binding  basicHttpBinding          bindingConfiguration  Secure        lt  endpoint gt   lt  service gt   lt bindings gt       lt basicHttpBinding          name  shortTimeout          timeout  00 00 00 01          gt        lt basicHttpBinding          name  Secure  gt           lt Security mode  Transport    gt        lt  basicHttpBinding gt   lt  bindings gt

User · Answer

I was using webHttpBinding and forgot to dicate the security mode of  Transport  on the binding configuration which caused the error      lt webHttpBinding gt       lt binding name  MyWCFServiceEndpoint  gt         lt security mode  Transport    gt       lt  binding gt     lt  webHttpBinding gt    Adding this in configuration fixed the problem

User · Answer

In my case i am setting security mode to  TransportCredentialOnly  instead of  Transport  in binding  Changing it resolved the issue   lt bindings gt     lt webHttpBinding gt       lt binding name  webHttpSecure  gt         lt security mode  Transport  gt           lt transport clientCredentialType  Windows   gt  lt  transport gt         lt  security gt         lt  binding gt     lt  webHttpBinding gt   lt  bindings gt

User · Answer

Make sure SSL is enabled for your server!

I got this error when trying to use a HTTPS configuration file on my local box which doesn't have that certificate. I was trying to do local testing - by converting some of the bindings from HTTPS to HTTP. I thought it would be easier to do this than try to install a self signed certificate for local testing.

Turned out I was getting this error becasue I didn't have SSL enabled on my local IIS even though I wasn't intending on actually using it.

There was something in the configuration for HTTPS. Creating a self signed cert in IIS7 allowed HTTP to then work :-)

User · Answer

I think you are trying to configure your service in a similar way to the following config  There is more information here  Specify a Service with Two Endpoints Using Different Binding Values  Also  other than for development  it s probably not a good idea to have both HTTP  amp  HTTPS endpoints to the same service  It kinda defeats the purpose of HTTPS  Hope this helps    lt service type  HelloWorld  IndigoConfig  Version 2 0 0 0  Culture neutral  PublicKeyToken null  gt       lt endpoint         address  http   computer 8080 Hello          contract  HelloWorld  IndigoConfig  Version 2 0 0 0  Culture neutral  PublicKeyToken null          binding  basicHttpBinding          bindingConfiguration  shortTimeout       lt  endpoint gt       lt endpoint         address  http   computer 8080 Hello          contract  HelloWorld  IndigoConfig  Version 2 0 0 0  Culture neutral  PublicKeyToken null          binding  basicHttpBinding          bindingConfiguration  Secure        lt  endpoint gt   lt  service gt   lt bindings gt       lt basicHttpBinding          name  shortTimeout          timeout  00 00 00 01          gt        lt basicHttpBinding          name  Secure  gt           lt Security mode  Transport    gt        lt  basicHttpBinding gt   lt  bindings gt

User · Answer

I had this exact same problem   Except my solution was to add an  s  to the binding value   Old   binding  mexHttpBinding   New  binding  mexHttpsBinding   web config snippet    lt services gt       lt service behaviorConfiguration  ServiceBehavior  name  LIMS UI Web WCFServices Accessioning QuickDataEntryService  gt           lt endpoint behaviorConfiguration  AspNetAjaxBehavior  binding  webHttpBinding  bindingConfiguration  webBinding               contract  LIMS UI Web WCFServices Accessioning QuickDataEntryService    gt           lt endpoint address  mex  binding  mexHttpsBinding  contract  IMetadataExchange    gt       lt  service gt

User · Answer

It turned out that my problem was that I was using a load balancer to handle the SSL  which then sent it over http to the actual server  which then complained   Description of a fix is here  http   blog hackedbrain com 2006 09 26 how-to-ssl-passthrough-with-wcf-or-transportwithmessagecredential-over-plain-http   Edit  I fixed my problem  which was slightly different  after talking to microsoft support   My silverlight app had its endpoint address in code going over https to the load balancer   The load balancer then changed the endpoint address to http and to point to the actual server that it was going to  So on each server s web config I added a listenUri for the endpoint that was http instead of https   lt endpoint address    listenUri  http    LOAD BALANCER ADDRESS         gt

User · Answer

It turned out that my problem was that I was using a load balancer to handle the SSL  which then sent it over http to the actual server  which then complained   Description of a fix is here  http   blog hackedbrain com 2006 09 26 how-to-ssl-passthrough-with-wcf-or-transportwithmessagecredential-over-plain-http   Edit  I fixed my problem  which was slightly different  after talking to microsoft support   My silverlight app had its endpoint address in code going over https to the load balancer   The load balancer then changed the endpoint address to http and to point to the actual server that it was going to  So on each server s web config I added a listenUri for the endpoint that was http instead of https   lt endpoint address    listenUri  http    LOAD BALANCER ADDRESS         gt

User · Answer

Look at your base address and your endpoint address  can t see it in your sample code   most likely you missed a column or some other typo e g  https     instead of https

User · Answer

I was using webHttpBinding and forgot to dicate the security mode of  Transport  on the binding configuration which caused the error      lt webHttpBinding gt       lt binding name  MyWCFServiceEndpoint  gt         lt security mode  Transport    gt       lt  binding gt     lt  webHttpBinding gt    Adding this in configuration fixed the problem

User · Answer

Look at your base address and your endpoint address  can t see it in your sample code   most likely you missed a column or some other typo e g  https     instead of https

[wcf] https with WCF error: "Could not find base address that matches scheme https"

Examples related to wcf

Examples related to https