indexingservice issues over https

Azhar Mahmood

Vote:

IndexingService is throwing the following erros, but when you try to access the service at the urls

"https://stg.themarket.myteleflora.com/IndexingService/IndexingService.svc" - service page comes back ok with a message "Endpoint not defined"

"https://stg.themarket.myteleflora.com/IndexingService/IndexingService.svc/update/?accesskey=local" - service page comes back ok with a message "Method not allowed"

Exception Below:

015-07-29 08:35:21,105 [78] ERROR SearchSettings - Send batch for named index 'theMarketSearch' failed. Items are left in queue.
2015-07-29 08:35:51,282 [6] ERROR SearchSettings - Update batch could not be sent to service uri 'https://stg.themarket.myteleflora.com/IndexingService/IndexingService.svc/update/?accesskey=local'. Message: 'The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()

Please note that we have an iRule to redirect all the traffic to https and all other services are working fine over https. We had this issue prior to episerver 8 upgrade but was resolved by deleting the cms indexing andrebuilding it, but no luck after episerver 8 upgrade.

#131546

Jul 30, 2015 0:26

Azhar Mahmood

Vote:

Just tried to rebuild the indexing after removing old index, but got the following exception.

2015-07-29 17:27:35,597 [96] ERROR SearchSettings - Update batch could not be sent to service uri 'https://stg.themarket.myteleflora.com/IndexingService/IndexingService.svc/update/?accesskey=local'. Message: 'The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at EPiServer.Search.RequestHandler.MakeHttpRequest(String url, NamedIndexingServiceElement namedIndexingServiceElement, String method, Stream postData, Action`1 responseHandler)
   at EPiServer.Search.RequestHandler.SendRequest(SyndicationFeed feed, String namedIndexingService, Collection`1 ids)'
2015-07-29 17:27:35,599 [96] ERROR SearchSettings - Send batch for named index 'theMarketSearch' failed. Items are left in queue.

In case the exception in the first post is not visible, please see it here.

015-07-29 08:35:21,105 [78] ERROR SearchSettings - Send batch for named index 'theMarketSearch' failed. Items are left in queue.
2015-07-29 08:35:51,282 [6] ERROR SearchSettings - Update batch could not be sent to service uri 'https://stg.themarket.myteleflora.com/IndexingService/IndexingService.svc/update/?accesskey=local'. Message: 'The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()

#131547

Edited, Jul 30, 2015 0:30

Richly Chheuy

Vote:

Could you verify if your web.config comports with the suggested episerver search ssl configuration here - http://world.episerver.com/blogs/Eric-Pettersson/Dates/2014/5/Are-you-also-having-trouble-with-EPiServer-Search-IndexingServicesvc-and-SSL/

#131548

Jul 30, 2015 0:37

Azhar Mahmood

Vote:

I already did but here are a few other things I noted.

We have

Episerver.Commerce.* 8.13.2.721

EpiServer.Search.IndexingService 7.5.394.2

Location:

  <location path="IndexingService/IndexingService.svc">
    <system.web>
			<authorization>
				<allow users="*"></allow>
			</authorization>
      <httpRuntime maxQueryStringLength="65536" />
    </system.web>
    <system.webServer>
      <security>
        <requestFiltering>
          <requestLimits maxQueryString="65536" />
        </requestFiltering>
      </security>
    </system.webServer>
  </location>

Binding:

   <bindings>
      <webHttpBinding>
        <binding name="Secure">
          <security mode="Transport">
            <transport clientCredentialType="None" />
          </security>
        </binding>
        <binding name="IndexingServiceCustomBinding" maxBufferPoolSize="1073741824" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647">
          <readerQuotas maxStringContentLength="10000000" />
          <security mode="Transport">
            <transport clientCredentialType="None" />
          </security>
        </binding>

Search Config

<episerver.search active="true">
    <namedIndexingServices defaultService="theMarketSearch">
      <services>
           <add name="theMarketSearch" baseUri="https://stg.themarket.myteleflora.com/IndexingService/IndexingService.svc" accessKey="local"/>
      </services>
    </namedIndexingServices>
    <searchResultFilter defaultInclude="true">
      <providers />
    </searchResultFilter>
  </episerver.search>
  <episerver.search.indexingservice>
    <clients>
       <add name="local" description="local" allowLocal="true" ipAddress="172.26.50.1,172.26.51.1,172.16.193.197,172.16.194.50,172.16.194.51" readonly="false" />
    </clients>
    <namedIndexes defaultIndex="default">
      <indexes>
         <add name="default" directoryPath="\\tfokisilon.teleflora.net\stg_themarket\CMSIndex" readonly="false" />
      </indexes>
    </namedIndexes>
  </episerver.search.indexingservice>

#131602

Jul 30, 2015 17:12

Azhar Mahmood

Vote:

I was able to resolve it by adding both http and https bindings to the configs and and then buildingthe endpoint accordingly in IndexingService.svc . However I noticed that only http binding works, but not the https binding. Here is the post that helped me in this respect.

https://d2developer.com/blog/using-indexing-service-with-both-http-and-https/

#131607

Jul 31, 2015 0:12

Try our conversational search powered by Generative AI!

indexingservice issues over https