“I created the self-signed cert, double clicked on it and added it to the
Trusted Root Certification Authorities.”
Sorry I missed this. In that case, I stand corrected. The other next likely
possibility is hostname mismatch.
On Tue, Jul 2, 2024 at 6:03 PM Dmitri Maziuk
wrote:
> On 7/2/24 16:40,
Hi, By default solr uses managed schema and I updated to
classicIndexSchemaFactory in solrconfig.xml for the collection that I am
using and tried again. It worked for my use case since schema is
predefined for me. The lesson learnt is for predefined schema with
classicIndexSchemaFactory configurat
On 7/2/24 16:40, Rahul Goswami wrote:
Since you are using a self-signed certificate, the browser won't have a
corresponding CA certificate for it and hence flags it. The connection is
still encrypted as with usual SSL.
wrong:
I created the self-signed cert, double clicked on it and added it
This is expected. When you visit any website, the server sends its
certificate to the browser. The browser validates this certificate against
a pre-loaded CA certificate issued by a trusted authority (Verisign,
GoDaddy etc),
Since you are using a self-signed certificate, the browser won't have a
c
On 7/2/24 16:17, Hodder, Rick (Property and Casualty CIO) wrote:
Any idea what I'm doing wrong?
What is the actual error? -- Images usually get stripped off on the
mailing lists and this list is no exception.
Dima
I am trying to get SOLR SSL Enabling set up on a Windows server.
I am trying to get it working with a self signed certificate, as is described
in the reference guide
I created the self-signed cert, double clicked on it and added it to the
Trusted Root Certification Authorities.
I adjusted Solr
Bingo. We do not have a field called "set", but we do have this line as
our final field definition:
So it must have been simply ignoring the "set". I removed that line just
to test it, created a new collection, indexed a single document, and was
able to do the atomic update.
Thanks for the i
Hi Jeremy,
If the collection you're having the problem with has a schema with a field
named 'set', you might be running into
https://issues.apache.org/jira/browse/SOLR-17274.
Cheers,
Calvin
On Mon, Jul 1, 2024 at 3:39 PM Jeremy Buckley - IQS-C
wrote:
> I can reproduce the error on a fresh coll
Hi Sathish:
Did you find a resolution to this issue? What jdk version are you
running in each case?
Michael
On Mon, Jun 17, 2024 at 2:39 PM Oleksandr Tkachuk wrote:
>
> Try to disable security manager. It can affect all requests, including
> update requests.
> I updated solr version from 8.4.0 to
