Antonio Villegas

Hi @catbegemot, thanks for contacting us. With respect to the problem you described, you can ping https://api.neliocontent.com/time (GET request) from your server.

It seems that your server is blocking requests to external URLs. Please confirm that and if that’s the issue, contact your hosting provider in order to allow you make requests to our endpoint.

There was another customer facing the same problem you mentioned (API errors on both regular and non-SNI mode) and the cause was a firewall blocking everything on his server.

If the ping does work, please contact us via email to support.content at neliosoftware.com. We’ll provide further instructions there ??

Resolved. The update was released some days ago.

Closed because the problem is fixed.

Could you try again? We’ve made a new change in our servers. Maybe this fixes your problem.

No. If you delete the plugin (just deactivate, not clean and deactivate) you won’t lose anything.

For those of you with problems, please send us temporary admin access to your site (username and password, plus the admin URL of your site) to [email protected] and we’ll try to fix it for you.

However, note that if the problem persists after updating the plugin to the latest version, it may be caused due to the cache. The only change in the new version is the URL to access Nelio Content API.

Hope this helps.

You should clean your caches and force reload in your browser. If the update to 1.2.11 worked well, everything should be right. Otherwise, uninstall the plugin and install it again.

Just update to the last version (1.2.11) to fix the issue.

Hi Dale,

Sorry about the late response. That warning you copied here has nothing to do with the issue. In fact, it is just a warning, so don’t worry about that. Anyway, we’ve improved the way we sync with our cloud servers using several attempts. We are internally testing this out and we’ll release an update soon.

I see the problem now. When WordPress publishes a post, Nelio Content sends a notification to our servers in the cloud letting us now about the post publication so that we can start the process of sharing your messages to social networks.

That notification failed (our logs show that we didn’t receive it for these two posts). That explains why the messages didn’t come out automatically.

We’ll improve the way this notification works (adding an automatic retry system in the plugin so that we can make sure the notification arrives to our cloud). However, could you please take a look at your PHP error log in your server? Please let us know if you find some error logs (timeouts, errors, whatever strange you see) there at the publication time of these two posts. Your case is the first one having problems sending the notification to our cloud.

If you find that the error logs contain sensitive data, please email us that info to support.content at neliosoftware dot com.

Thanks for your collaboration, Dale.

When did you realize the social messages hadn’t been auto-shared? Right after the post was published? A few minutes later? Much later? I’m asking because social sharing may take a couple of minutes since the post is published…

Hi Dale,

We took a look at our logs and apparently everything that was scheduled for 2017-04-12 was published properly. As an example, this Twitter message was published at 17:24 UTC, and its related post was published at that time too.

Can you please tell me what was wrong exactly?

Thanks!

We fixed the problem, therefore I mark this topic as resolved.

Hi @mrcarvallo,

You should first log in in Facebook or LinkedIn with the accounts you want to connect to Nelio Content. This way Nelio Content will connect to these accounts without any problem when you add them in Settings.

Also, make sure that you grant the permissions Nelio Content requires when connecting to Facebook and LinkedIn. If you revoke these permissions, Nelio Content won’t be able to connect to your profiles.

If you still have issues with this, please send us a screenshot showing the problem to [email protected].

We’re happy to help you fix this issue as soon as possible.

• This reply was modified 7 years, 8 months ago by Antonio Villegas.

Then probably the only thing you can do is ask your hosting provider to provide SNI support to your SSL calls. That surely will fix the communication issue with our API.

Talk to them and let us know, please.

Hi indental,

I’m Antonio, one of David’s partners here at Nelio and the responsible of Nelio Content’s API. Your problem may be caused because your server does not provide support for SNI. We’re using Amazon API Gateway to create our API with a custom domain name. Amazon’s documentation indicates that clients making requests to the API must be compatible with SNI (more info here).

Taking this into account, please check the following to see whether it fixes the issue or not:

1. Edit the file includes/class-nelio-content.php
2. Find the statement define( 'NELIO_CONTENT_API_URL', 'https://api.neliocontent.com/v1' ); around line 171.
3. Change it with define( 'NELIO_CONTENT_API_URL', 'https://qgr7l2qre9.execute-api.eu-west-1.amazonaws.com/v1' );
4. Try again using the plugin to see if it works

Please, once you do the previous steps let us know if everything worked or not.

Again, thanks for your collaboration. We really appreciate it!