Hi Sam,

I've tried to access in your Joomla backend, but it seems like you already changed the password, can you provide us again with your Joomla backend login credential so that we can take a look of this?

I have provided the password.

Hi Sam,

Thanks for getting back to us quickly, it seems like you're getting this error from the Facebook debugger tool result.

SSL_CONNECT_ERROR error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure

Take a look of your previous post thread http://stackideas.com/forums/sharethis-not-sharing#reply-192798

Can you try consult with your Webhosting provider this temporary delete the parameter -SSLv3 in SSL Cipher Suite in Apache Configuration then restart apache and see how it goes.

curl_setopt($ch, CURLOPT_SSL_CIPHER_LIST, 'SSLv3');

Hi Sam,

I missed up one of the screenshot.

Hi Arlex,

Before I do, I didn't have an issue with another post. Would you please try sharing another blog post? Thank you.

Hi Sam,

Yes, same issues even Facebook crawl the blog post image, if you look at the screenshot, i believe you can noticed the content is not get correctly.

By the way, I've tried do the global search about this, because you worry about the "Poodle" stuff in your site.

Can you take a look of this reference link for the solution?

http://stackoverflow.com/questions/28622558/how-to-solve-error-ssl23-get-server-hellosslv3-alert-handshake-failure
https://www.dwdonline.com/blog/fix-magento-error14077410ssl-routinesssl23_get_server_hellosslv3-alert-handshake-failure.html

Hi Arlex,

I've done enough reading on Poodle to believe that it is not as pervasive as originally feared. I will have them delete the parameter. Thank you.

Parameter deleted, Apache restarted, same issue. Any other suggestions, please?

Hi Sam,

Sorry for late reply to this,

We are almost there, can you provide us with your Facebook admin id ?

You can find your Facebook user id when you access -> https://graph.facebook.com/yourusername

Hi. I reached out to Cloudflare and they seem to have addressed an issue as well. I must be pretty determined to share my stupid posts on FB, huh?

The FB ID is attached under optional information.

Hi Sam,

Sorry for late reply to this,

I've help you updated your Facebook user ID in the Easyblog > social integration > Facebook LIKE setting, can you give it a try and see how it goes?

Resolved! Thank you very much!

Hi Sam,

You're welcome, glad to heard your issues resolved.

Mind if I ask what settings were changed? I noticed I am seeing a lot more requests to the server for each page load.

Hi Sam,

Sorry for late reply to this,

I have disabled with your JCH optimized plugin when i debugging last night. But after finish debugging, then I already help you enabled back and clear all the cache from backend.

I believe it because you enabled this "Send emails on page load" option, if your site have Easyblog pending email from backend, when you load your Easyblog page, it will process send the email to your user on page load.

What my suggestion is disabled that option and setup a cronjob in your site, so that it will automatically process and send out the email notification to your user. So it will not always send a lot of request to your server.

Thank you for your assistance. Yes, thank you. In the screenshot, the link on how to do a cronjob is showing a 404. Is there another resource available

Hello Sam,

You can refer on this documentation link for cronjobs, http://stackideas.com/docs/easyblog/how-tos/138-setting-up-cronjobs-in-cpanel

Yes, thank you. I was looking for the specific cronjob that would enable me to get notifications.

Hello Sam,

You are most welcome. Have you manage to create the cronjob for your easyblog?

No. The instructions in the link you provided just told me how to set up a cron in cpanel, but not which cronjob to set up.

Hi Sam,

I am sorry for the late reply.
I am not sure what do you mean by "which cronjob to set up". Are you referring to EasyBlog cronjob? You can use this command in your cronjob for EasyBlog:
/bin/wget -O /dev/null "http://yoursite.com/index.php?option=com_easyblog&task=cron

If you do not know how or unable to do this, perhaps you can provide us with your cPanel access so that we can help you setup cronjob for you.

Please advise.

Hi Arlex,

Thank you. Yes, I was looking for the specific cronjob to schedule in cpanel.

Please find attached my entry and the subsequent error. If it's possible to avoid sharing cpanel access, I'd appreciate it.

Thank you. I will advise if I have issues per the hosting provider. I appreciate the superior support.

Hello Sam,

You are most welcome. Keep us updated

The hosting provider did not have a solution. Please find temp cpanel access listed in site details

hello Sam,

Sorry for late reply to this,

Seems like your Wehosting provider can't help at all, we also can't do anything in your server.

because this error is related with your server wget have some security reason restrict user execute it.

ERROR 403: Forbidden.

By the way, can you try sign up an account from EasyCron and see how it goes?
https://www.easycron.com/

After you sign up, let us know.

Nope.

Dear User,

We're sorry to inform you that we are encountering a problem when trying to access the following URL:

http://marketsetc.com/index.php?option=com_easyblog&task=cron

The error we get is

HTTP/1.1 403 Forbidden (ErrorCode: 403)

The name of the problematic cron job is

EasyBlog

Please check the availability of the above URL and update the associated cron job on https://www.easycron.com if necessary.

Sometimes cron job failure is due to execution timeout of the cron job. Upgrading your plan (https://www.easycron.com/user/plan) will help increase the max timeout limit.

Best Regards,
EasyCron.com

Hi Sam,

I am really sorry for the delay of this reply as it is a weekend for us here.
Can i have your EasyCron.com access ?

Hi Arlex,

Changes that you made for a previous issue (reinstalling after my attempt with EZB 5A?) seem to have resolved the cronjob issue too. Hooray!!

Thank you.

--Sam

Hello Sam,

Really? that was strange.

If still not working, do refer back to us.

Yes, go figure.

Hello Sam,

Let us know if the problem still persists.