<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SOLR SSL Issues... in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/solr-ssl-issues/m-p/292547#M245677</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;It doesn't seem an SSL-specific issue (like self-signed certs), but it tells you that the connection was refused..! Maybe the server is not listening on the SSL port, please check that the tomcat server.xml configuration has the new keystore keys. I remember having a similar issue when installing a custom root chain. &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Aug 2014 08:53:45 GMT</pubDate>
    <dc:creator>mc128k</dc:creator>
    <dc:date>2014-08-19T08:53:45Z</dc:date>
    <item>
      <title>SOLR SSL Issues...</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/solr-ssl-issues/m-p/292546#M245676</link>
      <description>Hi Everyone,Our Alfresco-generated certificates recently expired, causing a repository outage.&amp;nbsp; We used the generate_keystores script that ships with Alfresco to generate new keystores.&amp;nbsp; It worked fine for the repository, which once again started cleanly with HTTPS.&amp;nbsp; However, the SOLR tracker can no</description>
      <pubDate>Thu, 07 Aug 2014 06:45:54 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/solr-ssl-issues/m-p/292546#M245676</guid>
      <dc:creator>rob_h</dc:creator>
      <dc:date>2014-08-07T06:45:54Z</dc:date>
    </item>
    <item>
      <title>Re: SOLR SSL Issues...</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/solr-ssl-issues/m-p/292547#M245677</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;It doesn't seem an SSL-specific issue (like self-signed certs), but it tells you that the connection was refused..! Maybe the server is not listening on the SSL port, please check that the tomcat server.xml configuration has the new keystore keys. I remember having a similar issue when installing a custom root chain. &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Aug 2014 08:53:45 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/solr-ssl-issues/m-p/292547#M245677</guid>
      <dc:creator>mc128k</dc:creator>
      <dc:date>2014-08-19T08:53:45Z</dc:date>
    </item>
  </channel>
</rss>

