WPSolar unable to to connect

Hi,

The error message is based on a Solr ping (/solr/core/admin/ping).
Please try to curl a ping to your Solr index from the WP server.

[root@localhost ~]# curl “https://192.168.203.153:8983/solr/collection1/admin/ping”

<?xml version=”1.0″ encoding=”UTF-8″?>
<response>
<lst name=”responseHeader”><int name=”status”>0</int><int name=”QTime”>2</int><lst name=”params”><str name=”spellcheck”>off</str><str name=”df”>text</str><str name=”echoParams”>all</str><str name=”rows”>10</str><str name=”echoParams”>all</str><str name=”q”>solrpingquery</str><str name=”distrib”>false</str></lst></lst><str name=”status”>OK</str>
</response>
[root@localhost ~]# curl “https://192.168.203.153:8983/solr/wordpress/admin/ping”

<?xml version=”1.0″ encoding=”UTF-8″?>
<response>
<lst name=”responseHeader”><int name=”status”>0</int><int name=”QTime”>1</int><lst name=”params”><str name=”spellcheck”>off</str><str name=”df”>text</str><str name=”echoParams”>all</str><str name=”rows”>10</str><str name=”echoParams”>all</str><str name=”q”>solrpingquery</str><str name=”distrib”>false</str></lst></lst><str name=”status”>OK</str>
</response>

Fine.

Can you show me a sreen capture of the WPSOLR admin page with the setup and error message ?

Is there a way to add a screen capture to this board?

Solr HTTP error: HTTP request failed, Failed to connect to 192.168.203.153: Permission denied (0)

Solr Protocol http
Solr Host 192.168.203.153
Solr Port 8983
Solr Path /solr/wordpress

(or /solr/#/wordpress, or mutliple other path variations, trying two cores, either of which can be queried using curl)

Thank you for creating with WordPress.

Version 4.1

I never got in all my tests a “Permission denied”.

That’s very strange.

I really have the feeling there is a blockage between both machines.

Try to gg “curl Permission denied”, there are some interresting similar issues out there.

That doesn’t really make sense. I can curl to query the solr just fine. I can access the solr using a browser just fine.

Why would a blockage only affect curl from within PHP, but not the command line?

Look in gg, there are issues with PHP/linux curl security, while curl command line works fine.

Okay – issue is:
Centos SELINUX security settings blocking curl under user apache. (Oddly, this was not reflected in any of the usual logs.)

Temporary workaround is to disable SELINUX