CRON ERROR: Content-type: text/html

[Paul]

Do you also get a 403 forbidden response if you run that link manually in your browser?

[mistresszhivago]

How can I get invoices to generate without the cron job? I can't get it to work and I need invoices to generate for annual/monthly services - thanks!

[Paul]

Invoices can only be generated via the cron, or by running the cron manually by clicking the link (Though I can't remember if the cron link exists in v 1.x, and we do not have a copy running I can check)

If you want to send me an admin login, I can take a look and confirm what the cron link should be. Once the link is confirmed, a cron should be able to be created using lynx, GET, or wget.

[krosenberg]

I'm having issues as well with cron and GoDaddy hosting as well, although I'm on 2.5.2. I am trying to set up a POP email address for support tickets, and cannot get the pop3-tickets cron to work.

If I copy and paste the code given to me in the CRON SETUP section at /a-settings.php?action=api into a new cron in the GoDaddy Cron Manager, exactly as it is in the input box, I get an emailed result after it runs saying:

 /bin/sh: php: command not found

Taking some advice the the previous messages in this thread, I tried doing Cron command:

/usr/bin/wget "http://mywebsite.com/clientsupport/cronjob.php?cron=pop3-tickets&key=8digitkey"

And that returned:

--14:10:01--  http://mywebsite.com/clientsupport/cronjob.php?cron=pop3-tickets&key=8digitkey
Resolving mywebsite.com... 123.456.789.01
Connecting to mywebsite.com|123.456.789.01|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 0 [text/html]
Saving to: `cronjob.php?cron=pop3-tickets&key=8digitkey'

    0K                                                        0.00 =0s

14:10:02 (0.00 B/s) - `cronjob.php?cron=pop3-tickets&key=8digitkey' saved [0/0]

Prior to running the cron, I sent an email to the email I set up in Support Departments, but it did not show up in Support Tickets. I have confirmed that the POP settings are correct for the email, and the system is set to receive emails from anybody, not just clients.

Also, when I click on the link to run the cron manually, I get:

Finished generating invoices! Logging to cron log. Attempting to apply any loose credits to open invoices. Attempting to charge any auto-debit accounts with invoices due soon. Attempting to deliver any invoices queued for delivery by e-mail. Done, logging to cron log. Attempting to update renew dates for services which have already renewed. Done, logging to cron log. Building clientrevenue graph data. clientrevenue graph data completed successfully. Building invoicedamt graph data. invoicedamt graph data completed successfully. Building invoices graph data. invoices graph data completed successfully. Building newclients graph data. newclients graph data completed successfully. Building revenue graph data. revenue graph data completed successfully. Building services graph data. services graph data completed successfully. Building services_canceled graph data. services_canceled graph data completed successfully. Attempting to unsuspend services that are now paid. No services needed to be unsuspended. ftp backup not configured

If I replace the "all" in address bar with pop3-tickets and hit Go, I get a blank browser.

Also, if it matters, the cron folder is in my root public html folder, which is one level up from /clientsupport.

[Paul]

It sounds like the path to cron is correct, since running all manually produces output.

Take a look at your phpinfo, if you create a php file with the following code in it it will show you this..

PHP Code:

<?php phpinfo(); ?>

And search for imap. The pop tickets feature requires the imap extension be loaded, it's a pretty common one so I would expect Godaddy to have it.

You can also try to turn on error_reporting and see if running it manually produces an error. In inc/config.php you can change error_reporting(0); to error_reporting(E_ALL & ~E_NOTICE); and see if any errors are returned.

[Marco]

Go Daddy can not process the "key" information in our cron jobs. So using the .php cron info, everything past .php will throw GoDaddy into a failure. Take out the key info and it will run the job, but Blesta will not. GD sends you an email saying its ok fine, but Blesta did not run the job.

I could not find a work around on this so I had to move hosting, I went to hostmonster.com/promo and I'm up and running.

I tried everything I could think of with Godaddy to make it work, no go.

Thats my 2 cents

Marc

[Paul]

Thanks for the update, and glad things are running well with the new hosting company now. Godaddy may be the only hosting company that can't run cron jobs with parameters.

We'll take a look, see if there is any workaround for the future.