We use Lynx to call urls by way of cron within a cpanel account we manage.
Recently the scripts stopped running and we tracked it down to Lynx throwing an error "Cannot access start file".
Lynx is used to access secure urls when these scripts are run and this is where the problem appears to be.
If I run /usr/bin/lynx --dump http://website_name using the unsecured protocol then everything works whereas https: throws the error above.
Intrigued I issued /usr/bin/lynx --dump https://another_domain_on_server from within the same account I'm having trouble using the shell and it worked seamlessly. In fact I tried several other secured domains and they all worked as expected.
The "only" difference with the site I am having problems with is the site uses a common or garden comodo certificate after ssls.com stopped selling the one we've always bought in the past.
Anyone had similar issues with this or have any idea why this should be a problem. Bit weird.
Thanks.
Recently the scripts stopped running and we tracked it down to Lynx throwing an error "Cannot access start file".
Lynx is used to access secure urls when these scripts are run and this is where the problem appears to be.
If I run /usr/bin/lynx --dump http://website_name using the unsecured protocol then everything works whereas https: throws the error above.
Intrigued I issued /usr/bin/lynx --dump https://another_domain_on_server from within the same account I'm having trouble using the shell and it worked seamlessly. In fact I tried several other secured domains and they all worked as expected.
The "only" difference with the site I am having problems with is the site uses a common or garden comodo certificate after ssls.com stopped selling the one we've always bought in the past.
Anyone had similar issues with this or have any idea why this should be a problem. Bit weird.
Thanks.