I tried to configure preemptive authentication by modifying the HttpPoster class, but I still get the same errors. Then I ran the following command in order to analyze the traffic: tcpdump -w /tmp/chatter.dmp -s 0 -i ens192 -X host solr-test01.uio.no
I'm not an expert in reading such outputs, but I can send you the dump file, Karl. I don't want to let the file be available for others, even though it's from our test environment. Erlend On 13/12/2018 15:09, Karl Wright wrote: > Ok, thanks, I misunderstood where the SSL error was coming from. The > Solr connection is what is complaining. Do you see "Connection working" > for your output connection? Please forgive me if you already answered > this; I didn't note it in your response. If you see that, then the > connector was able to talk to your Solr "ping" handler, which would mean > that the SSL configuration is right but there's something else about the > connection that we would have to figure out and deal with. > > Karl > > > On Thu, Dec 13, 2018 at 8:58 AM Erlend Garåsen <e.f.gara...@usit.uio.no > <mailto:e.f.gara...@usit.uio.no>> wrote: > > On 13/12/2018 14:26, Karl Wright wrote: > > This is SSL. Did you add the server's cert to the web connector's > > keystore? Or, if not, add a "trust all" rule? > > Thanks for the reply, Karl. > > Yes, the root certificate was added both in the repository connection > and for the Solr connector. > > I checked the "trust all" option and restarted the job. Same problem. > > BTW, I get a lot of 200s, so MCF is able to fetch the URLs. > > I have attached a screenshot of what I can see in the simple history > report. > > Erlend >
