Unable to open cron url Unknown SSL protocol error

lgisch

Hello,

I have this error message when I try to do indexation of one of the filters:
Unable to open cron url: Unknown SSL protocol error in connection to www.[domain].com:443

If I open manually cron url it gives the '...done' message, but the indexation of the filter is not done.

What should be checked?

Thank you!

saguaros

Hi lgisch

Did you try to create new cron URL for the filter? https://prnt.sc/qezryg

lgisch

Hello,
Yes, I tried it, it doesn't help. There is the same error. But I see now the result on frontend that the indexation is working.
What more must I check?
Thank you!

saguaros

lgisch

I need a closer look to see the issue, kindly share admin + ftp account of your site.

https://www.joomlart.com/forums/d/772-how-to-ask-a-question-on-forum

lgisch

Hello,
I updated the information.
Thank you!

saguaros

Hi lgisch

Is your host good enough? as we tried to update code to speed up the export process of the filter but your host is too slow for this task.

If you clone your site to local host, you can see that everything will work normally. You should consider to upgrade your hosting.

Regards

lgisch

Hello,
I have just contacted my hosting provider. He sad: Currently you are having the shared hosting server and currently we do not find slowness in the server.
He made some changes and is asking about the speed now.
Can you try again to do what you wanted?
Is it working now?

saguaros

Unable to open cron url: Unknown SSL protocol error in connection to www.[domain].com:443

You can ask your host for help to check this error as it relates to server issue.

I recommend you to move to a better hosting.

lgisch

Hello,
What exactly should be better in features for hosting in order to avoid the last error?
Thanks

lgisch

Hello,
The server administrator says that:
"Currently, I am unable to find a recent error in error log related to the JA Mega Filter Component. It appears like error related to the component ' JA Mega Filter'. The free SSL is enabled for your domain 'artgallery514.com'. It appears like component is unable to detect SSL type enabled for your website. Could you please contact the component vendor or check-in their support forums for known issues with this component. You can also contact their support and get back to us with the server requirements to run this component."
Let me know your suggestions please.
Thank you!

saguaros

lgisch

As the error indicates that the host can't open the ssl, kindly check with host on this.

Or you can simply take a test in another host, it will work normally.

lgisch

Hello,
I cloned my site to localhost and try to test it on XAMPP with php 7.3.
Now, if I make 'Index all' in MegaFilter component I see this error message:

Unable to open cron url: SSL certificate problem: self signed certificate

How would you recommend me to test MegaFilter extansion in localhost to check if changing of hosting helps to solve the previous issue with 'unkown SSL protocol error'?

Thank you!

saguaros

lgisch

In localhost, go to Backend > Components > JA Megafilter > Cron > Create a new cron URL >> Save it and check again.

lgisch

Hello,
I did exactly the same before I wrote the previous message. But it did not work.
What more could I try on this localhost site clone in order to find the cause of the issue?
Thank you!

saguaros

lgisch

Could I take a backup or your site and check in my local?

lgisch

Not yet, please. I'm trying to clone the site to a new hosting to see how it will work.
I will let you know.
Thank you!

saguaros

lgisch

Let me know then.

lgisch

Hello!
I have a god news. I did not clone the site to other hosting yet but used other solution and it works now.
I'm passing all traffic through cloudflare servers and everything in JA MegaFilter extension started to work. I don't see that ssl error anymore.
Based on this information, can you say what could be wrong for MegaFilter without cloudflare ?
Thank you!

saguaros

lgisch

JA Megafilter should work well with / without Cloudflare, as I mentioned above, this error relates to your server side as the error message indicated.