By William DAVIES on Thursday, 26 March 2020
Posted in Technical Issues
Replies 1
Likes 0
Views 620
Votes 0
In setting up a cronjob in cPanel, your documentation mentions:

You will need to get the correct wget path and replace the domain name above with your site's domain. Every hosting has a different /bin/wget. Please consult with your hosting provider for further explanation.

As you suggested in an earlier post, i contacted my hosting provider and their response was:

As the domain imdren.com is the main domain of the cPanel account, that site's path is home/imdrenco/public_html. That means your site's path is just right for wget like this https://imdren.com/index.php?option=com_easydiscuss&task=cron

I have tried the commands:

wget https://imdren.com/index.php?option=com_easydiscuss&task=cron

and

/usr/bin/wget -O /dev/null “http://imdren.com/index.php?option=com_easydiscuss&task=cron";


Both of the above commands produce an error email with the content:

--2020-03-26 11:24:01-- https://imdren.com/index.php?option=com_easydiscuss&task=cron
Resolving imdren.com (imdren.com)... 212.53.86.120
Connecting to imdren.com (imdren.com)|212.53.86.120|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/null’

0K 1.12M=0s

2020-03-26 11:24:02 (1.12 MB/s) - ‘/dev/null’ saved [18]




Nothing works whatever I try.

Before I give up on this, is there anything else either you or other posters could suggest.

Thanks in anticipation

Bill
Hello,

The response from wget is actually correct and those aren't errors. When the cronjob executes with >/dev/null , it basically means send the output to the trash so that the cron will not generate temporary files on your hosting unnecessarily.

Is there still a problem even when the cronjob is running?
·
Thursday, 26 March 2020 20:34
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post