Error connecting to the server

We are on the way to verify if these servers are blocking all outgoing requests, or just ours for some reason.
The solution is getting closer, hang on a few days until we come up with the fix, or publish which setting on the server should be changed.
Have a nice weekend !

In the update 1.0.13 a “curl” and “file_get_contents” call test is included in the plugin settings page, and we display the corresponding YES or NO.
Currently we use curl. If we found servers where curl fails but file_get_contents works, we implement the fall-back to the second.
We wait the reports, and hopefully one of these will work on the currently failing servers, then we can solve the issue.

in the 1.0.15 we fall back from curl to file_get_contents, and that is not working, we try the wp_remote_post. All of them have tests in the plugin settings.

The last one is even a wordpress function. So if none of these work, this means that there is a problem with the wordpress hosting, the provider should be contacted.

We included 4 prerequisite checks in the plugin’s settings page.

If none of the 3 protocols work, or the https (443) port is closed, we notice the admin that this is probably a firewall issue on the hosting provider.

If you have this problem, you can contact your hosting provider directly to open the port, and/or enable curl, and file_get_contents.
Or contact us sending the results of the checks from the settings page, and the name of your hosting provider.

This is a neat idea.

Site: knowlengr.com (LAMP)

Maybe RSS feed-generated content confuses it?
Also, the “Feedback report a problem” popup has a confused URL and is trying to send to a gopubmed address (yep!), which coincidentally appears in the log.

Here’s the log

Site is not local, but you’re detecting it as such.

https://www.knowlengr.com

Wed, 26 Jun 2013 21:09:14 +0000: Error connecting to the server.
Wed, 26 Jun 2013 21:09:14 +0000: Couldn’t resolve host ‘testiflocal’
Wed, 26 Jun 2013 21:09:14 +0000: Request url: testiflocal?url=https://KNOWLENGR.COM/wp-content/plugins/kaimbo-semantic-search/localtest.php
Wed, 26 Jun 2013 21:09:14 +0000: Your website address is detected as a local addres, not accessible from the internet. Kaimbo can not work.
Wed, 26 Jun 2013 21:09:29 +0000: Error connecting to the server.
Wed, 26 Jun 2013 21:09:29 +0000: Operation timed out after 10 seconds with 0 bytes received
Wed, 26 Jun 2013 21:09:29 +0000: Request url: https://gopubmed.org/web/websitesearch/register?base=https://KNOWLENGR.COM/&accesskey=7f8372b1-df04-45af-a447-742103c9f5e5
Wed, 26 Jun 2013 21:09:29 +0000: Connection failed when registering the website at the search service.
Wed, 26 Jun 2013 21:09:29 +0000: ERROR:28-Operation timed out after 10 seconds with 0 bytes received

p.s.suggest you log version info as well

Hallo knowlengr

Thanks for your report, we are looking forward to hear about the experience using Kaimbo.

We analyzed the servers logs as well, and we see that the first registration request timeouted, but it was successful just a few seconds later.

There can be 2 possible cause of the timeout:
Theoretically it is possible that our server was busy for a short while, and did not respond in time.
The other cause may be what I also experienced now with your page, that when I opened it, it was loading for a long time. After loading it once it works fine. (and looks nice by the way ?? )
This can be also the cause why we detected the site as local at first.

So currently we see that the site is indexed, and the search is working.
(is the search box available only for the admin users ?)

Sending requests to gopubmed.org is correct, this is the server holding the indexing and searching service currently. We will switch it to services.kaimbo.com soon.

We would be happy to receive suggestions and opinions about the plugin also in the future.