CSV CRON import is not working
- Ken Lee
- New Member
- Posts: 17
I once had this problem. In my case I found that it was caused by my multi-lingual setting which redirects accesses to index.php to /en/. Then I needed to add "/en" in the middle of the URL. Don't know if it is your case, but worth seeing. Check your apache access log and see any 301 return codes. Please check also, by verbose curl output to see any terms about redirect.
Here is the Akeeba Backup command I use, and is working just fine (the xxxxxx are manually done by me):
/opt/cpanel/ea-php71/root/usr/bin/php /home/xxxxxxxxxx/public_html/cli/akeeba-backup.php --profile=1 >/dev/null 2>&1
yes, manually everything is working fine!
I am hosting on my own servers by the way (CentOS 7.4 with cPanel / WHM). The Cron url I am using is:
Unfortunately I cannot give you access to the backend, because of EU privacy regulations.
I hope you can help me anyway
Is the Import working fine when you do it manually? The Cron command works for most of the servers. If It's not working, you can get in touch with your hosting support team share the vData Cron URL and get the Cron command. If it still doesn't work, please share your backend & FTP login credentials via Contact us form, We'll look into it.
I have implemented a CRON in order to import a CSV file. In the backend everything is working just fine, but the CRON is not working.
When manually type in the following command (in terminal session) "curl www.xxxxxxxxx.nl/index.php?option=com_vd...port&type=4S2q3RIAQA", the following result is shown:
 Done curl www.xxxxxxxxx.nl/index.php?option=com_vdata
 Done task=set_import
After that, nothing is happening. The file is not imported and in the backend the Hits field keeps showing me the same number over and over again: 0
Looks to me that the "type=4S2q3RIAQA" part is not used while running the CRON
Is there something wrong in the automatically generated CRON command (by vData)