[snfpaper]

7 months, 2 weeks ago #35686

We are receiving the following error when attempting to index some media files that are not yet part of the index:

Error on line 176 of file C:\WebSites\snfpaper.johndaniel.com\wp-content\plugins\wpsolr-pro\wpsolr\core\vendor\solarium\solarium\src\Core\Client\Adapter\Http.php: file_get_contents(https://localhost:8983/solr/snfpaper2/update/extract?omitHeader=true&extractOnly=true&extractOnly=0&wt=json&json.nl=flat&resource.name=2008-03-19.pdf): failed to open stream: HTTP request failed!

We are not sure what this error means or how to troubleshoot it. We do know that we attempted to locate the file listed in the error and could not locate it in the Media Library. We did, however, locate it on the drive. Thanks.

[wpsolr]

7 months, 2 weeks ago #35689

We did, however, locate it on the drive

What is “the drive”?

[snfpaper]

7 months, 2 weeks ago #35691

Our server.

[wpsolr]

7 months, 2 weeks ago #35693

Try to find the faulty media with this procedure:
– Index with batch size “1”
– When you see the error, redo the same but with option “debug” on, to see the debug trace
– Check for the media post_id in the debug trace
– Open the media to try to figure out the problem

[snfpaper]

7 months, 2 weeks ago #35696

We attempted to do this as you suggested. When we check the box across from the debug and ran the indexing, nothing showed up aside from the initial error (posted above). We tried clicking the hyperlink where it says: “Display debug infos during indexing”. However, this just brought up a pop-up telling us to reactivate our site license. We already reactivated it several days ago, since it had expired. So, we aren’t sure why this pop-up continues to appear.

[wpsolr]

7 months, 2 weeks ago #35697

The error occurs before the debug trace, hence the absence of logs.
I noticed your solr url is https://localhost:8983. This kind of error message can happen if you do not use a self-signed CA certificate with https.

[snfpaper]

7 months, 2 weeks ago #35699

We have several websites on our server. We are using let’s ectrypt certs for https. Where can we change localhost to the actual server name so the bindings match? Or do we need to put localhost in the bindings for this site? We are using IIS.

[wpsolr]

7 months, 2 weeks ago #35701

Can you try without https?

[snfpaper]

7 months, 2 weeks ago #35708

In 0. Connect your indexes, the scheme was already set for http.

[wpsolr]

7 months, 2 weeks ago #35709

Why does your trace error mention https://localhost:8983/solr/snfpaper2/update/extract?… ?

[snfpaper]

7 months, 2 weeks ago #35710

We do not know. Where do we configure that?

[wpsolr]

7 months, 2 weeks ago #35711

I then advise to create a new index with http, and see if logs continue to show https.

[snfpaper]

7 months, 2 weeks ago #35730

How do we do that? It has been a while since we created the initial index and we can’t remember what to do. Thanks.

[wpsolr]

7 months, 2 weeks ago #35731

You can follow the video at https://www.wpsolr.com/guide/configuration-step-by-step-schematic/configure-your-indexes/connect-to-an-apache-solr-index/

[snfpaper]

7 months, 2 weeks ago #35732

We are running Solr 7.4.0 on Windows Server 2016. We received the following error when we tried to create the index in Step 0:

We could not join your search server. Your path could be malformed, or your search server down (error code 400)

{ “responseHeader”:{ “status”:400, “QTime”:53}, “error”:{ “metadata”:[ “error-class”,”org.apache.solr.common.SolrException”, “root-error-class”,”java.lang.ClassNotFoundException”], “msg”:”Error CREATEing SolrCore ‘snfpaper’: Unable to create core [snfpaper] Caused by: solr.CaffeineCache”, “code”:400}}

We already downloaded the .zip file and placed it where the instructions indicated when we received this error.